I had this in Cyanogen's thread but I figured I'd pull it out of there because 1) his great work doesn't need to be corrupted by my miniscule offerings and 2) other people may want to see this.
If anyone is looking to get the IM app working on other builds, it's doable now.
You'll need to grab Cyanogen's build and yank some stuff out of it, specifically:
Need to do the following:
Grab the following files from the Cyanogen build:
/system/framework/com.android.im.plugin.jar
/system/app/IM.apk
/system/app/ImProvider.apk
/system/app/TmoImPlugin.apk
/system/lib/libwbxml.so
/system/lib/libwbxml_jni.so
/system/lib/libxml2wbxml.so
You'll need to push those files to the same directories on the build that you're using (haykuro, whatever) - copy them all to the same local directory on your pc or something, then adb remount, then adb push them to the appropriate directories (as listed above)
then do an adb shell reboot and you should have it working. FWIW I haven't been able to get yahoo IM working, but really..if you're using yahoo messenger, you are probably one of those people who want video ringtones, and I don't have any desire to help you
I just extracted the following from Dude's Cupcake 1.2 Full and installed them using appmanager. No ADB pushing and everything works great, including Yahoo messenger. I am currently using Dude 1.1a lite.
IM.apk
ImProvider.apk
TmoImPlugin.apk
MetalMessiah78 said:
I just extracted the following from Dude's Cupcake 1.2 Full and installed them using appmanager. No ADB pushing and everything works great, including Yahoo messenger. I am currently using Dude 1.1a lite.
IM.apk
ImProvider.apk
TmoImPlugin.apk
Click to expand...
Click to collapse
That worked perfectly with Haykuro's ION build. Fantastic find mate. Cheers.
Neither approach seems to work on the Rogers rom.
As soon as I boot up:
"The process com.google.process.gapps has stopped unexpectedly. Please try again. Force close"
I get this error 2 or 3 times consecutively before I can use the phone. The IM app doesn't show up at all. Back to a 3rd part app I suppose. Thanks for the info anyways
This method DOES NOT work on any of the hero roms. The IM app force closes on launch.
Add the files plz ?
Any chance you can add the required files to the post ?
danigman said:
Any chance you can add the required files to the post ?
Click to expand...
Click to collapse
Here ya go.
afflaq said:
I had this in Cyanogen's thread but I figured I'd pull it out of there because 1) his great work doesn't need to be corrupted by my miniscule offerings and 2) other people may want to see this.
If anyone is looking to get the IM app working on other builds, it's doable now.
You'll need to grab Cyanogen's build and yank some stuff out of it, specifically:
Need to do the following:
Grab the following files from the Cyanogen build:
/system/framework/com.android.im.plugin.jar
/system/app/IM.apk
/system/app/ImProvider.apk
/system/app/TmoImPlugin.apk
/system/lib/libwbxml.so
/system/lib/libwbxml_jni.so
/system/lib/libxml2wbxml.so
You'll need to push those files to the same directories on the build that you're using (haykuro, whatever) - copy them all to the same local directory on your pc or something, then adb remount, then adb push them to the appropriate directories (as listed above)
then do an adb shell reboot and you should have it working. FWIW I haven't been able to get yahoo IM working, but really..if you're using yahoo messenger, you are probably one of those people who want video ringtones, and I don't have any desire to help you
Click to expand...
Click to collapse
Hi, I used adb and followed your instructions, but I can't get the IM app up and running. I even used this post as a reference:
http://forum.xda-developers.com/showpost.php?p=3851087&postcount=319
I adb rebooted and after running the IM app, I get this:
"The process android.process.acore has stopped unexpectedly. Please try again."
I tried re-running it several times and I get the same error message. Any pointers? Thanks in advance!
-out
I also tried these steps on the Roger's build. I also got the same errors. I wonder what's different with this build that won't allow the IM app to install?
i tried the adb push n that didnt do the trick....i just installed the 3 apk files with the package installer from linda file manager n it did the trick.....
thank you guys
gringo69 said:
i tried the adb push n that didnt do the trick....i just installed the 3 apk files with the package installer from linda file manager n it did the trick.....
thank you guys
Click to expand...
Click to collapse
Im on JF 1.51 ADP and just installed the three .apk's too
It also worked Thanks a lot i've been looking for this for awhile now.
pantlessjim said:
That worked perfectly with Haykuro's ION build. Fantastic find mate. Cheers.
Click to expand...
Click to collapse
You are welcome. Glad it worked for you.
JUST TO CLARIFY. This only works on Google builds, such as Dude, ION, JF, etc, which most already include as default anyway, minus ION. If you are using an HTC build, like some of the Haykuro or Rogers build, it will not work. The HTC framework is different from the Google framework, and unless someone patches them to work, they won't. Don't know enough about each framework that I can patch them.
If you are able to get those files from an HTC build, in theory, they should work with other HTC builds, but I don't think one exists with those files at the moment. Sorry.
gringo69 said:
i tried the adb push n that didnt do the trick....i just installed the 3 apk files with the package installer from linda file manager n it did the trick.....
thank you guys
Click to expand...
Click to collapse
SWEET!!! Finally i have my IM's back!
I am on the "Cyanogenized Rogers Rom" and I tried this just for the hell of it. It failed.. obviously... so I pulled the logs using log collector. Maybe if someone knows what they are doing they can look at the logs that I got. I just pulled what I thought was important...
Code:
D/PackageManager( 114): Scanning app dir /system/framework
D/PackageManager( 114): Scanning app dir /system/app
D/dalvikvm( 114): GC freed 6807 objects / 381744 bytes in 140ms
I/PackageManager( 114): /system/app/ImProvider.apk changed; collecting certs
D/dalvikvm( 114): GC freed 3530 objects / 193256 bytes in 118ms
E/PackageManager( 114): Package com.android.providers.im signatures do not match the previously installed version; ignoring!
I/PackageManager( 114): /system/app/TmoImPlugin.apk changed; collecting certs
D/dalvikvm( 114): GC freed 5357 objects / 367768 bytes in 120ms
D/installd( 45): DexInv: --- BEGIN '/system/app/TmoImPlugin.apk' ---
D/dalvikvm( 130): DexOpt: load 11ms, verify 3ms, opt 0ms
D/installd( 45): DexInv: --- END '/system/app/TmoImPlugin.apk' (success) ---
I/PackageManager( 114): /system/app/im.apk changed; collecting certs
D/dalvikvm( 114): GC freed 6082 objects / 364680 bytes in 144ms
I/PackageManager( 114): New shared user android.uid.im: id=10052
D/installd( 45): DexInv: --- BEGIN '/system/app/im.apk' ---
D/dalvikvm( 131): DexOpt: load 152ms, verify 914ms, opt 34ms
D/installd( 45): DexInv: --- END '/system/app/im.apk' (success) ---
W/PackageParser( 114): Intent filter for activity ActivityIntentInfo{43895b38 com.android.contacts.ContactsPreferenceActivity} defines no actions
W/PackageManager( 114): Skipping provider name android.server.checkin (in package com.android.providers.htcCheckin): name already used by com.google.android.server.checkin
D/PackageManager( 114): Scanning app dir /data/app
W/PackageParser( 114): Skipping non-package file: /data/app/com.rerware.android.MyBackupPro.zip
W/PackageParser( 114): Skipping non-package file: /data/app/com.maize.digitalClock.zip
D/dalvikvm( 114): GC freed 9219 objects / 534392 bytes in 141ms
W/PackageParser( 114): Skipping non-package file: /data/app/com.schwimmer.android.hidenseek.zip
D/PackageManager( 114): Scanning app dir /data/app-private
I/PackageManager( 114): Time to scan packages: 16.536 seconds
W/PackageManager( 114): Removing dangling permission: com.android.providers.im.permission.WRITE_ONLY from package com.android.providers.im
W/PackageManager( 114): Removing dangling permission: com.android.providers.im.permission.READ_ONLY from package com.android.providers.im
W/PackageManager( 114): Unknown permission com.android.email.permission.READ_ATTACHMENT in package com.google.android.apps.uploader
W/PackageManager( 114): Unknown permission com.android.providers.im.permission.READ_ONLY in package com.android.im
W/PackageManager( 114): Unknown permission com.android.providers.im.permission.WRITE_ONLY in package com.android.im
For fun, try pushing these through adb from the 1st post.
/system/framework/com.android.im.plugin.jar
/system/lib/libwbxml.so
/system/lib/libwbxml_jni.so
/system/lib/libxml2wbxml.so
I'm thinking that might be required to get it working on HTC roms, but if it overwrites something that the htc rom needs, it might cause problems with something else.
The Google roms must already have the information contained in these files and thus not require that they be pushed. I would do a Nandroid back up first, push the files, and test everything out. If you start getting weird problems, Nandroid back to your backup.
st00p1d question on AT&T with ADP1
This just isn't gonna work for me, is it.
@MorphWVUtuba Here's what I've gathered so far. If you're using a Google build then you should be able to get T-Mo's IM installed. However, you're SOL if you're on an HTC build.
Thanks for the reply. I have JF build, which IIRC is a Google build. I get an error saying "unable to read your phone number" off of the sim card. Do you or anyone else know what that means?
Thanks a lot guys, i've been looking for this for a while now n& everything is working perfectly.
For all of you running HTC roms that have been unable to make IM work, Dude just released a Rogers rom with IM included. Try pulling the files from his rom and see if it works. It might give those of you who haven't been successful a better chance of making this work. Even if you can't just copy over the apk's, he might have patched up he framework files.
I would try the apk's first. If that doesn't work, adb the framework files and apk's like the first post suggests.
Related
So I wanted VoiceDialer on my stock ADP1. I grabbed VoiceDialer.apk from JFv1.31_ADP1.zip and installed it using adb (sdcard mounted on computer, so it wasn't mounted on the phone). It runs, and I was quite satisfied with its recognition abilities, but when it comes to clicking "OK" to dial, it always crashes with a "force close" dialogue. Holding the "send" button does bring up the VoiceDialer program. My guess is I'm missing some sort of configuration somewhere. Does anyone know?
Make sure you grabbed the VoiceDialer.odex too, if there is one.
Koush said:
Make sure you grabbed the VoiceDialer.odex too, if there is one.
Click to expand...
Click to collapse
I didn't find any odex files (unless they would be in recovery.img, which I haven't yet learned how to open). These files are not created automatically?
Unzip a RC30 update.zip and look in \system\app\
On ADP1, the dex is created at runtime by the dalvikvm from the classes file inside the zip. On RC30, the dex files for the builtin apps are created ahead of time and stored alongside the apk. This prevents the system from using up \data partition space with dex files (As the ADP1 build does).
jashsu said:
Unzip a RC30 update.zip and look in \system\app\
On ADP1, the dex is created at runtime by the dalvikvm from the classes file inside the zip. On RC30, the dex files for the builtin apps are created ahead of time and stored alongside the apk. This prevents the system from using up \data partition space with dex files (As the ADP1 build does).
Click to expand...
Click to collapse
I was able to find a copy of VoiceDialer.odex as per your description, but if I understand you correctly, that will not solve my problem.
If the dev phone uses dex files instead, and these are created at runtime, then I would expect to find a dex file for VoiceDialer if everything is working properly. Indeed, the file "[email protected]@[email protected]" exists.
Any other hints as to why the application might crash after clicking "OK" to dial a number?
Yeah just grab the VoiceDialer.apk from JF's modified ADP1 build. It contains the classes.dex file required to run on ADP1 build.
jashsu said:
Yeah just grab the VoiceDialer.apk from JF's modified ADP1 build. It contains the classes.dex file required to run on ADP1 build.
Click to expand...
Click to collapse
That's what I did initially. That part all seems to work.
Doh, went around in a circle ;-) I thought we were talking about the RC30 version.
Yeah you'll have to ask JF about this since I think he compiled VoiceDialer from source for his ADP mod build. There is no odex file to look for.
jashsu said:
Yeah you'll have to ask JF about this since I think he compiled VoiceDialer from source for his ADP mod build.
Click to expand...
Click to collapse
Yeah, I'm sure JF could see the problem real quick. I'm real timid about bothering people, though - I was hoping he might swing by this thread by chance. What's considered appropriate on this forum: PM? E-mail? IM? Visitor Message?
IMSargon said:
Yeah, I'm sure JF could see the problem real quick. I'm real timid about bothering people, though - I was hoping he might swing by this thread by chance. What's considered appropriate on this forum: PM? E-mail? IM? Visitor Message?
Click to expand...
Click to collapse
Your best bet is IRC. A lot of us hang out in #android on Freenode.
IMSargon said:
So I wanted VoiceDialer on my stock ADP1. I grabbed VoiceDialer.apk from JFv1.31_ADP1.zip and installed it using adb (sdcard mounted on computer, so it wasn't mounted on the phone). It runs, and I was quite satisfied with its recognition abilities, but when it comes to clicking "OK" to dial, it always crashes with a "force close" dialogue. Holding the "send" button does bring up the VoiceDialer program. My guess is I'm missing some sort of configuration somewhere. Does anyone know?
Click to expand...
Click to collapse
Your best bet is to remount /system and push the .apk directly into /system/app. I haven't tried installing it with adb install, so I'm not sure if that's what is causing your problems or what.
JesusFreke said:
Your best bet is to remount /system and push the .apk directly into /system/app. I haven't tried installing it with adb install, so I'm not sure if that's what is causing your problems or what.
Click to expand...
Click to collapse
Yeah, I had the same problem (I've installed voice dialer using adb install)
Uninstalled in application manager, rebooted, remounted, pushed voicedialer.apk to /systemp/app, rebooted again, and it worked )
JesusFreke said:
Your best bet is to remount /system and push the .apk directly into /system/app. I haven't tried installing it with adb install, so I'm not sure if that's what is causing your problems or what.
Click to expand...
Click to collapse
It worked! Great! Thanks a ton!
------------------------------
Steps taken:
1. copy VoiceDialer.apk to phone
# adb push VoiceDialer.apk /sdcard/VoiceDialer.apk
763 KB/s (51125 bytes in 0.065s)
#
2. enter shell on phone, and gain root
# adb shell
$ su
#
3. mount the system partition as rewritable
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#
4. copy VoiceDialer.apk to the proper system directory
# cat /sdcard/VoiceDialer.apk > /system/app/VoiceDialer.apk
#
5. make permissions match the other files
# chmod 644 /system/app/VoiceDialer.apk
#
6. reboot the phone
# reboot
------------------------------
For extra credit, does anyone understand why this happens? What does it tell us about how apps work and install?
adb pushing the apk directly bypasses the PackageManager. By using adb install, the package manager will run (as if the package was installed from the Market or Browser). There are various reasons the PackageManager might reject a package, including inability to run dexopt, incompatibility with existing data registered to an older version of an app, etc. A list of errors that would block an apk installation is here. Look at the constants starting with INSTALL_FAILED and INSTALL_PARSE_FAILED.
jashsu said:
adb pushing the apk directly bypasses the PackageManager. By using adb install, the package manager will run (as if the package was installed from the Market or Browser). There are various reasons the PackageManager might reject a package, including inability to run dexopt, incompatibility with existing data registered to an older version of an app, etc. A list of errors that would block an apk installation is here. Look at the constants starting with INSTALL_FAILED and INSTALL_PARSE_FAILED.
Click to expand...
Click to collapse
Interesting, but in this case the application did not fail to install. The installation went normally, and the application functioned normally up to the point where it attempted to interface with another application/subsystem (whatever dials the phone).
IMSargon said:
Interesting, but in this case the application did not fail to install. The installation went normally, and the application functioned normally up to the point where it attempted to interface with another application/subsystem (whatever dials the phone).
Click to expand...
Click to collapse
When you install it with adb install, it gets installed as a normal (non-system) application. This can be verified by checking /data/system/packages.xml:
Code:
<package name="com.android.voicedialer" codePath="/data/app/VoiceDialer.apk" [B]system="false"[/B] ts="1232083952000" userId="10029">
<sigs count="1">
<cert index="0" />
</sigs>
</package>
One of the permissions it requires is "android.permission.CALL_PRIVILEGED". Based on the info in frameworks/base/core/res/AndroidManifest.xml (in the git source):
Code:
<permission android:name="android.permission.CALL_PRIVILEGED"
android:label="@string/permlab_callPrivileged"
android:description="@string/permdesc_callPrivileged"
[B]android:protectionLevel="signatureOrSystem"[/B] />
You can see the protectionLevel is "signatureOrSystem", meaning that the application has to be a system application in order to use that permission. Since the voice dialer was not installed as a system application, it can't be assigned that permission.
To confirm this, I tried installing the voice dialer with adb install, and then took a look at the logcat output, which contains the following line:
Code:
01-15 23:32:32.903: WARN/PackageManager(56): Not granting permission android.permission.CALL_PRIVILEGED to package com.android.voicedialer (protectionLevel=3 flags=0x44)
However, when you copy the apk to /system/app, it gets installed as a system application, which can be verified again by looking at /data/system/packages.xml:
Code:
<package name="com.android.voicedialer" codePath="/system/app/VoiceDialer.apk" [B]system="true"[/B] ts="1232084484000" userId="10035">
<sigs count="1">
<cert index="0" />
</sigs>
</package>
So it is able to use the "android.permission.CALL_PRIVILEGED" permission. After coping the apk to /system/app, I checked the logcat output and there was no mention of not being able to grant the android.permission.CALL_PRIVILEGED permission, as expected.
Interestingly enough, copying the file to /system/app doesn't bypass the package manager. The package manager is watching both /data/app and /system/app for new files, and it automatically installs anything you copy into either location. It also does an uninstall when you delete an apk from either location.
JesusFreke said:
Interestingly enough, copying the file to /system/app doesn't bypass the package manager. The package manager is watching both /data/app and /system/app for new files, and it automatically installs anything you copy into either location. It also does an uninstalls when you delete an apk from either location.
Click to expand...
Click to collapse
I didn't know that. In that context it does make sense why it would disallow call permission if put into /data/app
Offtopic, but are you planning on creating a modified version of the newly released ADP1 "1.1" build?
Thanks, JF, your explanation makes the problem quite clear!
Has anyone tried pushing in Default Android Calendar to any of the SenSe/Hero ROM.
I've tried pushing it in following this Hero post without success.
http://forum.xda-developers.com/showthread.php?t=554826
Any ideas welcome.
I'm on eViL v1.5 currently.
s11
EDIT : ok. I managed to get it working on Hofo 3.0.5 following the above steps. but I really like to get it to work on eViL's ROM.
Alright,
I've tried with Hofo's ROM. Stock cupcake Calendar.apk pushed in successfully and works.
I tried pushing the same Calendar.apk to eViL's SenSe ROM and got the following in adb logcat.
E/PackageManager( 1714): Package com.android.calendar has no signatures that match those in shared user android.uid.calendar; ignoring!
W/PackageManager( 1714): Package couldn't be installed in /data/app/com.android.calendar.apk
Any idea how to get around this?
Great. got it solved.
followed this thread http://forum.xda-developers.com/showthread.php?t=503007 to get Calendar.apk auto-signed, put it in /sdcard and install through Astro.
I've also renamed SenSe Calendar.apk as Calendar2.apk.
Have now both Stock Android Calendar and Sense Calendar.
credit to mixpix405 on the auto-signing post.
I installed the MoDaCo Custom Rom r3.1 and it's perfect except for 1 tiny little thing: the default HTC contacts app has been renamed from 'People' to 'HTC People' (actually, from 'Contacten' to 'HTC Contacten' in my localized version of MCR).
I decided to unpack the HtcContacts.apk using apktool and replace all occurrences of 'HTC People' with just 'People'. Then, I repacked everything into an .apk and signed it with a key. Then, I pushed the new HtcContacts.apk to /system/app/ while in recovery mode. However, the new contacts app does not show up after booting ... might this be caused by using a random key for signing? If so, how should I sign this apk to make it work?
The whole thing should have been signed with test keys when it was de-odexed. The only other thing is that it could have been re-packed wrong, or you need to update the packages.xml.
I'm quite new to this odex stuff, so I don't know much about it. I'm usually 'just' a developer.
What's the deal with this 'test keys' stuff? Do you mean that I should find a specific key to sign the apk with?
No, I mean don't sign it again after you edit it.
-------------------------------------
Alias::NeO on HTC Desire
Well, that's what I tried first. To be more concise:
1. I flashed MCR r3.1 to my device and kept it in recovery
2. I took the HtcContacts.apk from the update zip that I used in step 1
3. I used apktool to unpack it, since all resources were in binary format in the apk itself
4. I edited the appropriate resources
5. I repacked everything into a fresh HtcContacts.zip
6. I pushed the new HtcContacts.zip to /system/app/
7. After the very first boot of MCR r3.1, the Contacts app was invisible in the app drawer
Since that obviously didn't work, I decided to sign the apk before pushing it to /system/app/ but that yielded the exact same result.
Do I need to sign the APK with the same key that is used for the other apks in /system/app?
alias_neo said:
No, I mean don't sign it again after you edit it.
Click to expand...
Click to collapse
You must resign files after any change made to them. If we wouldn't have to do it, then whole signing idea would have no sense.
franklinvv said:
What's the deal with this 'test keys' stuff? Do you mean that I should find a specific key to sign the apk with?
Click to expand...
Click to collapse
franklinvv said:
Do I need to sign the APK with the same key that is used for the other apks in /system/app?
Click to expand...
Click to collapse
Yes, and they were probably signed using testsigner tool. Did you used testsigner last time? If not, then try it.
Also looking into logcat would be helpful - to be sure, that problem is related to signing.
I'm not sure where to find the testsigner that you mention ... but I used some testsign.jar that I found somewhere. Using that jar, I get this:
I/PackageManager( 151): /system/app/HtcContacts.apk changed; collecting certs
E/PackageManager( 151): Package com.android.htccontacts has no signatures that match those in shared user android.uid.shared; ignoring!
Click to expand...
Click to collapse
Also, I read (almost) everywhere that that testsign stuff is used for signing update zips. Can I still use it for signing APKs?
franklinvv said:
Also, I read (almost) everywhere that that testsign stuff is used for signing update zips. Can I still use it for signing APKs?
Click to expand...
Click to collapse
I don't know. But some time ago I wanted to replace my framework-res.apk file and I had to create update.zip file and sign it using testsign tool. So I think you are right.
Brut.all said:
I don't know. But some time ago I wanted to replace my framework-res.apk file and I had to create update.zip file and sign it using testsign tool. So I think you are right.
Click to expand...
Click to collapse
Right about what? That I should put it in an update.zip? And if so, do I still need to sign the APK that I will put in the update.zip or is that unnecessary?
Are you flashing or pushing the file?
franklinvv said:
Right about what? That I should put it in an update.zip? And if so, do I still need to sign the APK that I will put in the update.zip or is that unnecessary?
Click to expand...
Click to collapse
I think you have to create update.zip with unsigned file, then sign update.zip file using testsign and install it from recovery.
eViL D: said:
Are you flashing or pushing the file?
Click to expand...
Click to collapse
I'm pushing it ... I will try flashing it now. (Never knew that there really was a difference between those 2 methods.)
Brut.all said:
I think you have to create update.zip with unsigned file, then sign update.zip file using testsign and install it from recovery.
Click to expand...
Click to collapse
I'm trying that right now.
Argh ... whatever I do, my update-script keeps yielding syntax errors!
This is all that I have in the update-script:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:app
show_progress 0.1 10
Click to expand...
Click to collapse
I put the HtcContacts.apk in a /system/app subdir.
When I try to flash the zip, it fails with 'E:Syntax error in update script', and /tmp/recovery.log tells me:
Install from sdcard...
Finding update package...
I:Update location: SDCARD:update-signed.zip
Opening update package...
I:Update file path: /sdcard/update-signed.zip
Verifying update package...
I:Verified META-INF/CERT.RSA
I:Verified META-INF/MANIFEST.MF
I:Verified META-INF/com/google/android/update-script
I:Verified system/app/HtcContacts.apk
Installing update...
line 1: syntax error at '0.1'
E:Syntax error in update script
Installation aborted.
I:Set boot command ""
Click to expand...
Click to collapse
I have NO idea what I'm doing wrong.
Try: "show_progress 0.100000 0". But I don't know much about update.zip creating.
If I try that, it tells me:
line 1: syntax error at 'show_progress'
Click to expand...
Click to collapse
Edit: I'm all out of ideas ... I think I'll have to give up.
Edit2: After playing around with the update-script and trying stuff with the show_progress lines, I finally removed the lines and that worked after the 2nd try.
Unfortunately, my own HtcContacts.apk STILL doesn't work ...
I/PackageManager( 328): /system/app/HtcContacts.apk changed; collecting certs
E/PackageParser( 328): Package com.android.htccontacts has no certificates at entry AndroidManifest.xml; ignoring!
I/PackageManager( 328): Failed verifying certificates for package:com.android.htccontacts
Click to expand...
Click to collapse
So the APK does need to be signed before putting it in the update.zip?
you don't need:
set_perm_recursive 0 0 0755 0644 SYSTEM:app
Thanks, I changed the update-script accordingly.
However, I ended up with this:
I/PackageManager( 190): /system/app/HtcContacts.apk changed; collecting certs
E/PackageManager( 190): Package com.android.htccontacts signatures do not match the previously installed version; ignoring!
Click to expand...
Click to collapse
And after the second boot, I get this:
I/PackageManager( 151): /system/app/HtcContacts.apk changed; collecting certs
E/PackageManager( 151): Package com.android.htccontacts has no signatures that match those in shared user android.uid.shared; ignoring!
Click to expand...
Click to collapse
So, I'm stuck now ... I have the feeling that Paul signed everything in the MoDaCo ROM with an unknown key?
Hi,
I baked a CM-7.0.3 based ROM with the kitchen, from which (among others) I removed GTalk and QuickOffice. I flashed the ROM with recovery and it works perfectly, but strangely I find
Code:
/system/apps/Quickoffice.apk
/system/apps/Talk.apk
on the phone.
I verified that in the WORKING dir (of kitchen) and in the zip I baked these files are not present (also not other apks like com.google.android.talk) and I whiped the cache and dalvik cache after flashing the ROM.
So where do these come from?!
When I logcat the very first boot with the new ROM, I see 2 lines containing Quickoffice, which read:
Code:
D/installd( 117): DexInv: --- BEGIN '/system/app/Quickoffice.apk' ---
D/dalvikvm( 211): DexOpt: load 435ms, verify+opt 5939ms
D/installd( 117): DexInv: --- END '/system/app/Quickoffice.apk' (success) ---
and the same for Talk.apk.
Does anyone have an idea how to get rid of these?
BTW I'm S-ON, so I always do my modifications to /system in my kitchen WORKING dir and bake updated ROMs as needed.
TIA!
Boot to recovery, go to advanced, then select "format /system" then reflash your modified ROM
Sent from my GT-P1000 using XDA App
Thanks! I'll try that. meanwhile I removed the apks from a shell in recovery after mounting /system, but of course that would be an extra step after the next ROM update. still funny though that it happens, since I thought the updater script already formats /system?
cheers
Sent from my Legend using XDA App
powerpenguin said:
Thanks! I'll try that. meanwhile I removed the apks from a shell in recovery after mounting /system, but of course that would be an extra step after the next ROM update. still funny though that it happens, since I thought the updater script already formats /system?
cheers
Sent from my Legend using XDA App
Click to expand...
Click to collapse
It kinda does, but it backs up certain files and puts them back after flashing. It definitely does this to gapps (including talk) and it may do it to others too.
Sent from my GT-P1000 using XDA App
Hi,
I wrote a little script with some nice utilities to customize the Kindle Fire HDX 8.9.
Options available :
Superuser
Remove signature check
Install Google Apps
Fix wallpaper
It runs under Linux, and you need to have java, jar, sed, wget, adb and aapt set up on your computer.
To use it, plug your device and enable adb.
Extract the archive and run hdx.sh in a terminal.
Everything is not perfect, but it seems to work pretty good for me
Thanks to everybody who worked on the tools I use in this script.
Is play store working for downloading
Sent from my SPH-L900 using xda app-developers app
Tanks to cpasjuste tips it is
I know u mentioned Linux us it possible to run this from windows
Sent from my SPH-L900 using xda app-developers app
I have the same question... can we run this script under windows somehow. I already have root, gmail and music working... play store can't connect though... I also used adb to do the wallpaper fix and it says it is applied but nothing seems to have happened. Still no wallpapers anyway. btw, I also have superuser and busybox installed too.
Same question here. Also, can the wallpaper fix be used stand alone and will we be able to have wallpapers on stock launcher? I am on 7“
Sent from beneath my invisibility cloak
Judging by the content of the .sh file, i believe a .bat file can be written to run on windows... however, it would be prudent to do it in a safestrap rom slot, you know, just in case something goes wrong...
Thanks for sharing @Ptiwee !
Ill try manual execution of some of the steps in your guide (most especially on the ones related to DownloadProvider) and see how it goes !
Cheers!
If you want just the wallpaper fix I thought I'd mention my fix still works on the hdx that I designed for the HD, though you may have to install busybox on your kindle first.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
It should be possible to use it on Windows, though you have to find the equivalent for all programs used inside (especially for sed ...)
I don't have time to care about it before Christmas ...
stunts513 said:
If you want just the wallpaper fix I thought I'd mention my fix still works on the hdx that I designed for the HD, though you may have to install busybox on your kindle first.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Do i have to be rooted?
Sent from beneath my invisibility cloak
Will this allow Amazon Appstore to work?
It doesn't look like it as you've used the same cm10 apks, but I thought it wouldn't hurt to ask before I go through the trouble of trying it out...
Sent from my KFTHWI using Tapatalk 4
Hanzo.Hasashi said:
Do i have to be rooted?
Click to expand...
Click to collapse
You'll need to root before applying the wallpaper fix
Sent from my KFTHWI using Tapatalk 4
I have tried this and after applying the Google Apps 3rd option it rebooted and now its stuck with the kindle fire logo and not coming up anymore
The device answers to adb commands (lists up with adb devices) and reboots with "adb reboot fastboot" and/or "adb reboot recovery"
Although resetting with the recovery to factory defaults doesnt help...
Anyone know whats happening? (I cant afford to send it back to US as I live in Colombia)
Sorry for the double post
Root works, but when trying the signature check (I just went past 1-2-3-4 and 5 without checking for errors I was just too sleepy)
It gives me this:
Waiting for device ...
Pulling files ...
8403 KB/s (3479504 bytes in 0.404s)
335 KB/s (27576 bytes in 0.080s)
5837 KB/s (1083168 bytes in 0.181s)
6180 KB/s (1505152 bytes in 0.237s)
9411 KB/s (10893168 bytes in 1.130s)
6375 KB/s (1398376 bytes in 0.214s)
1422 KB/s (130136 bytes in 0.089s)
4940 KB/s (765056 bytes in 0.151s)
7 KB/s (313 bytes in 0.040s)
1 KB/s (72 bytes in 0.040s)
Deodexing ...
Exception in thread "main" org.jf.util.ExceptionWithContext: services.odex is not an apk, dex file or odex file.
at org.jf.dexlib2.DexFileFactory.loadDexFile(DexFileFactory.java:111)
at org.jf.dexlib2.DexFileFactory.loadDexFile(DexFileFactory.java:54)
at org.jf.baksmali.main.main(main.java:247)
Editing /com/android/server/pm/PackageManagerService.smali ...
./hdx.sh: line 40: smali/com/android/server/pm/PackageManagerService.smali.new: No such file or directory
mv: cannot stat ‘smali/com/android/server/pm/PackageManagerService.smali.new’: No such file or directory
Recompiling ...
UNEXPECTED TOP-LEVEL EXCEPTION:
java.lang.RuntimeException: Cannot find file or directory "smali"
at org.jf.smali.main.main(main.java:174)
./hdx.sh: line 44: jar: command not found
rm: cannot remove ‘smali’: No such file or directory
rm: cannot remove ‘classes.dex’: No such file or directory
Reodexing on device...
7 KB/s (313 bytes in 0.040s)
push: scripts/remove_signature_check/dexopt-wrapper -> /data/local/tmp/dexopt-wrapper
push: scripts/remove_signature_check/odexsign.sh -> /data/local/tmp/odexsign.sh
2 files pushed. 0 files skipped.
70 KB/s (5822 bytes in 0.081s)
Signing and replacing services.odex ...
--- BEGIN 'services.jar' (bootstrap=0) ---
--- waiting for verify+opt, pid=6931
--- would reduce privs here
--- END 'services.jar' --- status=0xff00, process failed
20+0 records in
20+0 records out
20 bytes transferred in 0.001 secs (20000 bytes/sec)
Cleaning ...
Done, push any key to continue ...
Click to expand...
Click to collapse
Any ideas why services.odex is not what its looking for? (Maybe someone could upload it?)
Guys, if ANY PART OF THIS FAILS & YOUR DEVICE REBOOTS, IT WILL BRICK THE HDX.
Several people are having issues (maybe running this in a terminal on device or via mnty) that leads to the endless bootloop. This can also occur if there are files left in Dalvik cache from the old download manager & UI.
Use caution & common sense when trying to modify your device. My brother works for Amazon & has told me that they are supposed to start cracking down on device returns this week. If you mess your device up because you don't really know what you are doing (much of this is early developmental stage) there is an increasing chance that you will be stuck with a non-functioning device &/or out several hundred dollars.
Poesini said:
Sorry for the double post
Root works, but when trying the signature check (I just went past 1-2-3-4 and 5 without checking for errors I was just too sleepy)
It gives me this:
Any ideas why services.odex is not what its looking for? (Maybe someone could upload it?)
Click to expand...
Click to collapse
If you are still stuck in bootloop, I can help you. Based on your post, I bricked on purpose & was able to recover. Hit me up, or check out my thread in the HDX General forum section.
GSLEON3 said:
If you are still stuck in bootloop, I can help you. Based on your post, I bricked on purpose & was able to recover. Hit me up, or check out my thread in the HDX General forum section.
Click to expand...
Click to collapse
WOW
FKN WOW
You saved my life man you just saved my life... Followed your guide and now I have my device back again YAY
Thanks a lot man
Jocky & I probably saves 100's of Kaisers back in the WM days. Been a while since I've had time to really get into Android firmware, but I can still piddle with the best of the average, lol...
Glad you are fixed .
Now you can mod the build.prop & start anew if so desired. What I did. Once you've used the exploit, SU is almost garunteed to stay, at least until Amz patches it in an update.
Sent from my Nexus 7 using XDA Premium HD app
Ptiwee said:
Hi,
I wrote a little script with some nice utilities to customize the Kindle Fire HDX 8.9.
Options available :
Superuser
Remove signature check
Install Google Apps
Fix wallpaper
It runs under Linux, and you need to have java, jar, sed, wget, adb and aapt set up on your computer.
To use it, plug your device and enable adb.
Extract the archive and run hdx.sh in a terminal.
Everything is not perfect, but it seems to work pretty good for me
Thanks to everybody who worked on the tools I use in this script.
Click to expand...
Click to collapse
Hi,
I tried to install the Google Apps with the scripts, and now every time I boot up it shows "Kindle is upgrading ...."
After a while it still boot up successfully. But it is taking longer time.
Also, the Google Play store only works for me once after I first reboot. Afterward, it app closes itself right after I click on it.
Reboot does not help.
Did I do anything wrong here? Any idea how I can fix it?
Thanks.
I'm back from Christmas celebrations, sorry ...
As GSLEON3 stated, it is important to use those scripts safely. I put them here for crazy people who know what they are doing
The Kindle update is a known bug, it doesn't disturb me a lot but maybe I'll try to find a solution
For the Google Play store not working, did you disabled the signature check ?