Related
Link to apk file:
forum.xda-developers.com/showthread.php?t=624416
I'm running rooted stocked 2.1...5 with this mod installed. I tried to put it in the system/app folder because there is some room in there, since I removed some apps, but it did not like it. It just kept foreclosing it.
Any idea how to put it in there or even replace the original HTC_IME?
could have something to do with it being made for the nexus one
obsanity said:
Link to apk file:
forum.xda-developers.com/showthread.php?t=624416
I'm running rooted stocked 2.1...5 with this mod installed. I tried to put it in the system/app folder because there is some room in there, since I removed some apps, but it did not like it. It just kept foreclosing it.
Any idea how to put it in there or even replace the original HTC_IME?
Click to expand...
Click to collapse
i've made one from there, and installed it. I didn't push it to /system/app.
try doing that.
also make sure you are using the low res option.
obsanity said:
Link to apk file:
forum.xda-developers.com/showthread.php?t=624416
I'm running rooted stocked 2.1...5 with this mod installed. I tried to put it in the system/app folder because there is some room in there, since I removed some apps, but it did not like it. It just kept foreclosing it.
Any idea how to put it in there or even replace the original HTC_IME?
Click to expand...
Click to collapse
First make sure you downloaded the "lo" version, since Hero is low-res. And unpack the ZIP. It's not flashable, it's just zipped for convenience.
And then you can just install HTC_IME_lo.apk from your file manager by clicking it. There's no need to manually push it into /system/app. (It's registered differently from the default HTC_IME, so it can be installed like any normal application.) If you removed Clicker.apk while you were removing junk from /system/app, you'll need to reinstall that as well.
If you really want to replace the original HTC_IME, just rename HTC_IME_lo.apk to HTC_IME.apk and push it to /system/app. I think that's what you were trying to do before.
Hope this helps!
Oh, sorry I guess I forgot to mention that it is running fine in the user folder after installing it. It's just that I wanted to put in the system/app folder to save some space. I'll try renaming it and replacing with the stocked file. BTW, I'm typing on it now and its way better than the stocked because of how much customization you can do.
I finally tied this and it's a no go. Still get FC messages. However, all seems fine when I install it as an app. I think it's because the HTC_IME.odex file which is tied to the original. Even after rebooting it didn't work.
Anyone know how to get that odex file from the new HTC_IME I'm trying to install in the system/app folder?
As the subject line states: I've signed (successfully?) my custom ROM zip file using various programs/methods. Each of them claims a successful signed zip at the end. However, when I try applying my ROM via CWM, I get the standard E:sig verification failed error msg. (Of course, disabling the verification check in CWM allows my ROM to be installed, error-free).
Yes, I've been through all the signing tutorials (that I could find) on this board. A couple were quite useful, but all they did was confirm I was doing the procedure correctly.
Here's a bit of background on my ROM:
It's actually a collection of 4 types of APKs:
some stock, Sense stuff... presumably signed by HTC
some 3rd party (Market) APKs... presumably signed by the appropriate author
some of my own APKs (signed by me, with my own SSL key)
some of my own APKs (not signed at all)
I've also gone in and modified some existing stock HTC APKs.
I tell you this info because I think this is where the problem might be.
Is it possible to sign a ROM file only at the ZIP level (and thereby encompass all the APKs within it)?
If not, do I have to go inside the ROM and sign each APK individually? Do I need to sign them all, or only those that have changed? And which key do I sign it with? (mine? generic test?) Is there ever a scenario where I have to remove/replace an existing signature from an APK with my own signature? Do I need to remove any existing META-INF folders before attempting to sign anything?
These are the questions to which I could find no answers.
Any help would be greatly appreciated.
Thanks,
- Anthony
Tigger31337 said:
As the subject line states: I've signed (successfully?) my custom ROM zip file using various programs/methods. Each of them claims a successful signed zip at the end. However, when I try applying my ROM via CWM, I get the standard E:sig verification failed error msg. (Of course, disabling the verification check in CWM allows my ROM to be installed, error-free).
Yes, I've been through all the signing tutorials (that I could find) on this board. A couple were quite useful, but all they did was confirm I was doing the procedure correctly.
Here's a bit of background on my ROM:
It's actually a collection of 4 types of APKs:
some stock, Sense stuff... presumably signed by HTC
some 3rd party (Market) APKs... presumably signed by the appropriate author
some of my own APKs (signed by me, with my own SSL key)
some of my own APKs (not signed at all)
I've also gone in and modified some existing stock HTC APKs.
I tell you this info because I think this is where the problem might be.
Is it possible to sign a ROM file only at the ZIP level (and thereby encompass all the APKs within it)?
If not, do I have to go inside the ROM and sign each APK individually? Do I need to sign them all, or only those that have changed? And which key do I sign it with? (mine? generic test?) Is there ever a scenario where I have to remove/replace an existing signature from an APK with my own signature? Do I need to remove any existing META-INF folders before attempting to sign anything?
These are the questions to which I could find no answers.
Any help would be greatly appreciated.
Thanks,
- Anthony
Click to expand...
Click to collapse
Here is something that works if you decompile and recompile a apk take the res folder out the part you tweaked and throw it in one that wasn't tweaked or extracted and the Sig will be good.
Sent from my PG86100 using xda premium
reaper24 said:
Here is something that works if you decompile and recompile a apk take the res folder out the part you tweaked and throw it in one that wasn't tweaked or extracted and the Sig will be good.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Okay, so you're saying that signing at the level of the ROM ZIP simply isn't enough. (I wish the guides would say that).
You're saying, I will need to preserve the sigs on the original APKs? I get that. But now that raises more questions:
- when you say "decompile" an APK, I assume this is a simple unzip/extract? That's all I've been doing so far (I use 7-Zip).
- Say I now have an extracted APK (assume it was an HTC stock), I can inject my modified files. Piece of cake. I now have an HTC APK with my own data in there. But what about all the other APKs that make up my entire ROM? Do they ALL have to been signed the same way? (In this example, do they ALL have to be HTC signed?) I'm guessing NO, because there are apps in the data/apps directory from the Market, with their own vendor sigs. I can't see why I would have to re-sign those APKs using the HTC sig.
- So, we're back to my original question: can't you sign a ROM at the ZIP level, or do I have to go back into each individual APK inside that ROM and re-sign them all? Why would the original signature work, but not my own? I have generated my own SSL keys, so in theory I should be able to unzip a APK, tweak it, and re-sign it as my own.
Why does my ROM keep failing the signature test in CWM? I am looking for the necessary and sufficient conditions to allow my ROM (any ZIP file, really) to pass the signature verification check.
No one on this board has been able to answer that, so far.
Thanks so much,
- Anthony
Sorry if this is the wrong section to post this question,
My problem is with GO Dev's Theme Factory, importing an APK from a theme made in their old offline theme factory, then backing up the files into a Zip, modified the keystore.properties to match my settings and replaced the key store file by renaming mine to Android123.keystore and replacing inside the zip, yet when i re upload the backed up file and then try compiling into an APK i get errors regarding, KEYSTORE_PASS, STORE_PASS & STORE_ALIAS! I've emailed GO Dev but failed to make sense of them.
I've set key store & store pass to my Key store password when signing but no joy
Any help will be very much appreciated!
Cheers
Jason
Does any one know of an inverted Mms.apk or Gmail.apk that is not white for 4.4?
I have seen a few on here that are only flashable in recovery.
I am on Verizon with a locked BL.
Thanks!!
hackercity said:
Does any one know of an inverted Mms.apk or Gmail.apk that is not white for 4.4?
I have seen a few on here that are only flashable in recovery.
I am on Verizon with a locked BL.
Thanks!!
Click to expand...
Click to collapse
Mms (and Google black Dialer) could be find as described here: http://forum.xda-developers.com/showthread.php?t=2606281. I managed to push the attached inverted gmail to the system/app too (original renamed to Gmail2.apk.bak, renamed the inverted to Gmail2.apk, changed permissions to rw-r-r) and it worked without problems. Soon I got back to the stock app after I experienced notification "Unfortunatelly,Google services has stopped" after every reboot. Later I found out that services crashes because of ART and inverted Gmail has nothing with the issue.
Try 8sms app
Sent from my XT1053 using XDA Premium 4 mobile app
I have MMS but it is color option happy. It is my own work on the stock 4.4.1_r1 MMS app. If your into doing a butt load of colors pm me. Not enough post to post a link.
I made an inverted version of the cm mms app that I use. It works perfectly with stock rom including picture and video messaging. Allows you to send messages out to the groups in your stock contact app as well.
https://drive.google.com/file/d/0B0c5ipb1afd-RGFVVDZ6R0t4TWc/edit?usp=sharing
blackhand1001 said:
I made an inverted version of the cm mms app that I use. It works perfectly with stock rom including picture and video messaging. Allows you to send messages out to the groups in your stock contact app as well.
https://drive.google.com/file/d/0B0c5ipb1afd-RGFVVDZ6R0t4TWc/edit?usp=sharing
Click to expand...
Click to collapse
Blackhand EXCELLENT job! The most simple yet perfect one.
Sent from my Monster Moto X on KangaKat
Team Blacked Out has a ton of black apps.
http://www.designrifts.com/teamblackedoutapp/recently-updated-2/
8sms is a good replacement for MMS app.
Sent from my XT1055 using Tapatalk 2
grad061980 said:
Team Blacked Out has a ton of black apps.
http://www.designrifts.com/teamblackedoutapp/recently-updated-2/
8sms is a good replacement for MMS app.
Sent from my XT1055 using Tapatalk 2
Click to expand...
Click to collapse
Weird but I can not install none of this zips with TWRP - Failed status everytime
200mpx said:
Weird but I can not install none of this zips with TWRP - Failed status everytime
Click to expand...
Click to collapse
You can install them. Just extract apk from zip file, change original apk to apk.bak, push the new one to the same folder, give it original name, change permissions to rw-r-r and reboot. I've already installed inverted mms, gmail, play and music.
200mpx said:
Weird but I can not install none of this zips with TWRP - Failed status everytime
Click to expand...
Click to collapse
I do what piskr does, as I'm on the moto x & have a locked bootloader & no custom recoveries.
Sent from my XT1055 using Tapatalk 2
piskr said:
You can install them. Just extract apk from zip file, change original apk to apk.bak, push the new one to the same folder, give it original name, change permissions to rw-r-r and reboot. I've already installed inverted mms, gmail, play and music.
Click to expand...
Click to collapse
Tried to follow your receipt with Keep but it does not worked. SMS works fine but it was not extracted from zip
200mpx said:
Tried to follow your receipt with Keep but it does not worked. SMS works fine but it was not extracted from zip
Click to expand...
Click to collapse
That's true. SMS wasn't extracted from zip. But everything else were. Did you follow the instruction precisely? You must either rename the original apk files (to apk.bak) or move them to the sd card (you always have chance to get them back from there). Then you must rename the new apps as original ones were named. And copy them to the respective folders from where the original apps were taken. With explorer which could operate with system applications. Then change permissions for every new app to rw-r-r. And reboot the phone. You might be asked after to confirm your gmail login credentials and that's pretty all. You should have all black applications totally worked.
I'm attaching all inverted apps which I have actually installed. And they are the last versions available.
piskr said:
That's true. SMS wasn't extracted from zip. But everything else were. Did you follow the instruction precisely? You must either rename the original apk files (to apk.bak) or move them to the sd card (you always have chance to get them back from there). Then you must rename the new apps as original ones were named. And copy them to the respective folders from where the original apps were taken. With explorer which could operate with system applications. Then change permissions for every new app to rw-r-r. And reboot the phone. You might be asked after to confirm your gmail login credentials and that's pretty all. You should have all black applications totally worked.
I'm attaching all inverted apps which I have actually installed. And they are the last versions available.
Click to expand...
Click to collapse
Are we to only rename the original apk or do we also need to rename the odex file as well? I tried this on my N7 (2012) with the Gmail app and I am getting "Unfortunately, Gmail has stopped."
IT'S WORKING. I don't know why. Since it didn't work initially I renamed the original back from apk.bak to apk and renamed the inverted one blackGmail.apk and just left it in the system/app folder. It is now working but technically it shouldn't be working. Am I correct in my thinking that it shouldn't be working?
Thank You
DanRo80 said:
Are we to only rename the original apk or do we also need to rename the odex file as well? I tried this on my N7 (2012) with the Gmail app and I am getting "Unfortunately, Gmail has stopped."
Thank You
Click to expand...
Click to collapse
Gmail has probably stopped because the odex file is missing. The files I attached are deodexed and the original ones were as well. But, hey, you've got better solution - why shouldn't you give this toolkit a shot: http://forum.xda-developers.com/showthread.php?t=1766475. It looks like an easy way and you'll gain everything: unlock, root, custom recovery, restore option... And with custom recovery you can flash every black zip you wish from here: http://www.designrifts.com/teamblackedoutapp/recently-updated-2/, no need to seek for alternative solutions..:fingers-crossed:.
piskr said:
That's true. SMS wasn't extracted from zip. But everything else were. Did you follow the instruction precisely? You must either rename the original apk files (to apk.bak) or move them to the sd card (you always have chance to get them back from there). Then you must rename the new apps as original ones were named. And copy them to the respective folders from where the original apps were taken. With explorer which could operate with system applications. Then change permissions for every new app to rw-r-r. And reboot the phone. You might be asked after to confirm your gmail login credentials and that's pretty all. You should have all black applications totally worked.
I'm attaching all inverted apps which I have actually installed. And they are the last versions available.
Click to expand...
Click to collapse
piskr said:
Gmail has probably stopped because the odex file is missing. The files I attached are deodexed and the original ones were as well. But, hey, you've got better solution - why shouldn't you give this toolkit a shot: http://forum.xda-developers.com/showthread.php?t=1766475. It looks like an easy way and you'll gain everything: unlock, root, custom recovery, restore option... And with custom recovery you can flash every black zip you wish from here: http://www.designrifts.com/teamblackedoutapp/recently-updated-2/, no need to seek for alternative solutions..:fingers-crossed:.
Click to expand...
Click to collapse
I do have all of that on my N7 by using Wug's Toolkit. I was testing this first on the N7 before attempting this on my Moto X. It all is really to have it working on my Moto X.
DanRo80 said:
I do have all of that on my N7 by using Wug's Toolkit. I was testing this first on the N7 before attempting this on my Moto X. It all is really to have it working on my Moto X.
Click to expand...
Click to collapse
You have nothing to loose. As long as you keep original files somewhere you can always get back with just deleting modified and pushing into the system original ones.
piskr said:
You can install them. Just extract apk from zip file, change original apk to apk.bak, push the new one to the same folder, give it original name, change permissions to rw-r-r and reboot. I've already installed inverted mms, gmail, play and music.
Click to expand...
Click to collapse
I understand, I also managed to install mms, google music, hangouts, but failed with keep (that is most inetresting for me as I hate white stripe in widget) and google now.
By the way I found this topic with themed mms for 4.4.x - works fine for me (bubbles 2 version ). Have not tested contacts and dialer yet: http://forum.xda-developers.com/showthread.php?t=2519733
I can't seem to find Google Now Search or Play Store in the system to rename or copy the Blacked Out one to. What folder would they be in. I looked everywhere that I could think of.
DroidJunk said:
I have MMS but it is color option happy. It is my own work on the stock 4.4.1_r1 MMS app. If your into doing a butt load of colors pm me. Not enough post to post a link.
Click to expand...
Click to collapse
I tried to install via root explorer and it won't. What's the trick??
Sent from my XT1060 using xda app-developers app
mpetruzz said:
I tried to install via root explorer and it won't. What's the trick??
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Via RE you will also need to possibly wipe the dalvik file or the whole dalvik if you don't want to locate it. I did not post a link so I don't know which one you have. One had one with the odex and one didn't. If you have the single apk then you should also try to remove the odex file and reboot. Don't just click on the file in RE to install but copy it over. The flash should work via recovery. droidjunk.com/junk/Dev_MotoX_4.4_MMS.zip
I downloaded Sac's v2 ROM and I got used to the Recent apps where it usually is, my question is, is there anyway to flash a zip file or replace a file in order to achieve the stock button functions? I flashed his "hold home for recents" but its not the same as I'm used to.
You can take the android.policy.jar from system>framework in v1 and swap it and all buttons will go back to normal. (change permissions and such of course when replacing any system files)
I swapped the android.policy.jar files the other day, and as a result the phone just wouldn't boot. I'm guessing this is due to not setting permissions. How should permissions be set for the new file when it is swapped? And in addition, should permissions for other files placed in system be set the same exact way (for future reference)? I know how to change them, but do not know how they should be or why they should be set a certain way
dc.wash95 said:
I swapped the android.policy.jar files the other day, and as a result the phone just wouldn't boot. I'm guessing this is due to not setting permissions. How should permissions be set for the new file when it is swapped? And in addition, should permissions for other files placed in system be set the same exact way (for future reference)? I know how to change them, but do not know how they should be or why they should be set a certain way
Click to expand...
Click to collapse
The folder is set to rw-r-r- but there is a new flashable zip just posted in the sac23 thread
Not sure but I replaced the Android.policy.jar file from v1 to v2, worked like a charm. Took maybe 5 to 6 minuted to boot.