Related
I had a mod done to my widgetlocker apk , but i cant adb push it. Can someone please sign it for me so i can install using root explorer? Im not sure how difficult it is , so if its insanely hard or something im sorry for asking haha . Thanks .
Get apkmanager and it will sign it for you. Plus apk manager will let you decompile and recompile then sign so you can mod anything and it's a whole lot easier.
Sent from my Incognito Droid using Tapatalk
1. Add your JDK Directory to the Path variable (Right click on My Computer, Properties, Advanced, Environment Variables)
2. At the command prompt, navigate to the containing folder
3. keytool -genkeypair
4. jarsigner -verbose APPNAME.apk mykey
5. Push the signed app
sorry guys but im not real sure what a JDK directory is or anything. I didnt do the mod myself. i made a donation and had it done by someone on here. Once they returned it to me via email they told me to adb push it.. but i do not have any exp doing that and was hoping someone could help me out... there would be a nicely themed widgetlocker.apk in it for you haha
Different problem, same answer.
I have been trying to install a custom framework res for a while now. I am on a Mac. I simply have been changing ext to zip, unzipping, making changes, rezipping, using mv command in terminal to change to apk, and pushing to phone. It hasn't even kind of worked. Could someone please help? Are there any steps I'm missing? Do I need to sign the framework res apk?
Please help
lucas.scott said:
I had a mod done to my widgetlocker apk , but i cant adb push it. Can someone please sign it for me so i can install using root explorer? Im not sure how difficult it is , so if its insanely hard or something im sorry for asking haha . Thanks .
Click to expand...
Click to collapse
Post it or post a link to it and I'll sign it.
That said, if you modify one apk it is highly unlikely you will not modify others (which is a good thing). Therefore, I would highly recommend getting acquainted with the proper tools.
First you will need to install the Android SDK on your computer. Here is the link:
http://developer.android.com/sdk/index.html Bear in mind that to use it you will also need to install the JDK (Java Developers Kit) on your computer but the links are in the instructions so it is very easy.
In addition to the SDK download 7zip if you do not already have it. It is a free archive utility that enables opening and editing the contents of archives without extracting them.
Lastly, if you just plan on editing images download Stericson's autosign tool so that once you finish changing images you can resign the apk which is necessary to install. However, if you want to delve a little deeper into apps I highly recommend Apk Manager. Not only does it include a signing tool but can also decompile apks so that you can do deeper editing.
dkdude36 said:
I have been trying to install a custom framework res for a while now. I am on a Mac. I simply have been changing ext to zip, unzipping, making changes, rezipping, using mv command in terminal to change to apk, and pushing to phone. It hasn't even kind of worked. Could someone please help? Are there any steps I'm missing? Do I need to sign the framework res apk?
Please help
Click to expand...
Click to collapse
The framework-res.apk does not need to be resigned. In fact, there are few, if any, reasons why any system app would need to be resigned. Therefore, that should not be your issue.
That said, in the steps you listed above I see several areas which could problems so, it would be beneficial if you provided more information. Here are my initial comments:
1)When you are rezipping the apk are you recompressing the folder created when you unzipped the apk OR, are you selecting the contents of the folder (e.g. AndroidManifest.xml, res folder, etc. ) and compressing them? It is important to do it the second way I described.
2)No need to bother with the mv command as you are using it. Once you've rezipped the apk (it will likely be named Archive.zip) you will need to rename it "framework-res.apk" at which point you should only need to push the apk back to the phone. The process would go like this:
a)put modified framework-res.apk into the tools folder (located in the SDK folder)
b)open up terminal.app
c)type "cd " (without the quotes) and drag the tools folder located in the sdk folder into the terminal terminal window, and press Enter
d)type "./adb remount" (without the quotes) and press Enter
e)type "./adb push framework-res.apk /system/framework/" (without the quotes) and press Enter
f)type "./adb reboot" (without the quotes) and press Enter. (The phone will reboot which is necessary to see your changes)
g)Marvel at your accomplishment
Obviously, you should make a nandroid backup of your phone first so that in case you mess anything up you can restore it as if nothing happened.
If you have any more questions simply post them and I'd be happy to answer them. I bought and rooted my EVO the day it first came out which was before there were any Mac tutorials and have since become fluent in adb due to lots of trial and error.
could you possibly help me with my widgetlocker apk? i have adb pushed ( finally learned how to do that on mac) and it still wont install . have contacted ultralynx (he did the mod) but im not getting a response...thank you .
lucas.scott said:
could you possibly help me with my widgetlocker apk? i have adb pushed ( finally learned how to do that on mac) and it still wont install . have contacted ultralynx (he did the mod) but im not getting a response...thank you .
Click to expand...
Click to collapse
Hmmm... If ultralynx did the mod for you it is probably already signed. I've seen some of his threads and he clearly knows what he is doing. And, signing is apk-modding-101.
Where did you ./adb push the widget locker to? /system/app/ or /data/app/? Adb push does not install the apk if you push to /data/app/
My recommendation would be to do the following:
1)Using root explorer, find and delete the widgetlocker.apk from wherever you adb pushed it on your phone. Exit out of Root Explorer.
2)Reboot phone
3)Confirm that you don't have any previously installed versions of WIdget Locker on your phone. From your home screen press the menu button and navigate to Settings-->Applications-->Manage Applications-->All and look for Widget Locker. If you find it select and uninstall it.
4)Assuming the modified widget locker.apk was signed you should not need to mess with adb. You certainly can but it is not necessary and I'd hate to confuse you with the commands. So... Instead, connect the EVO to your computer and mount as disk drive. Put the widget locker.apk you want to install on your sdcard. Personally, I would recommend creating a folder named Apps and putting it in there.
5)Unmount phone as disk drive and unplug phone from computer
6) Using any file manager (Root explorer is fine) navigate to the apk on your sdcard and select install.
If that doesn't work let me know
Found problem, need answer
okolowicz said:
The framework-res.apk does not need to be resigned. In fact, there are few, if any, reasons why any system app would need to be resigned. Therefore, that should not be your issue.
That said, in the steps you listed above I see several areas which could problems so, it would be beneficial if you provided more information. Here are my initial comments:
1)When you are rezipping the apk are you recompressing the folder created when you unzipped the apk OR, are you selecting the contents of the folder (e.g. AndroidManifest.xml, res folder, etc. ) and compressing them? It is important to do it the second way I described.
2)No need to bother with the mv command as you are using it. Once you've rezipped the apk (it will likely be named Archive.zip) you will need to rename it "framework-res.apk" at which point you should only need to push the apk back to the phone. The process would go like this:
a)put modified framework-res.apk into the tools folder (located in the SDK folder)
b)open up terminal.app
c)type "cd " (without the quotes) and drag the tools folder located in the sdk folder into the terminal terminal window, and press Enter
d)type "./adb remount" (without the quotes) and press Enter
e)type "./adb push framework-res.apk /system/framework/" (without the quotes) and press Enter
f)type "./adb reboot" (without the quotes) and press Enter. (The phone will reboot which is necessary to see your changes)
g)Marvel at your accomplishment
Obviously, you should make a nandroid backup of your phone first so that in case you mess anything up you can restore it as if nothing happened.
If you have any more questions simply post them and I'd be happy to answer them. I bought and rooted my EVO the day it first came out which was before there were any Mac tutorials and have since become fluent in adb due to lots of trial and error.
Click to expand...
Click to collapse
Thanks for the help okolwoiz. I am fluent in adb and have been hacking for a while. I think I know the problem. The mod I was trying to theme (drop down notifications bar) is a .9.png, which means it is automatically resized to fit the phone. These are different than normal .png files. I know i need to use a draw9 something file in the sdk, but I don't know how. Any help would be great. Thanks
Dk
yeah i have tried all of that . It always just says "Application not installed" . No matter how i get it on the phone . ore than happy to send it to you to see if its the file or my phone .
Thanks this thread has helped me and I was just wondering through aimlessly.. And stumbled upon tis thread.
Sent from my netarchy_toast, froyo beast of a machine evo!
glad it helped someone haha
I'm trying to use my new Sensation with the SIM from my Japanese iPhone, which requires replacing the stock Mms.apk with one that works with Softbank. That much I managed to do. Now when I try to open the Messaging app it crashes immediately, which is apparently normal and means I need to delete the old Mms.odex. But when I try, the command prompt window tells me:
rm failed for /system/app/Mms.odex, No such file or directory
I've made sure the folder isn't read-only (I managed to copy the new Mms.apk to it after all). Not sure what else could be going wrong. Thanks in advance for any help.
Its not a good idea to push files into the system directory of an odexed ROM like that. You usually need to push the appropriate .odex file with the .apk file.
Also could be a permissions problem. You need to make sure the permissions for the new file the are same as what's already in the directory.
Sent from my Sensation using Cyanogenmod
dr.m0x said:
Its not a good idea to push files into the system directory of an odexed ROM like that. You usually need to push the appropriate .odex file with the .apk file.
Click to expand...
Click to collapse
I know it's not ideal, but this method seems to work just fine; I've read a bunch of Japanese blogs that explain this is how to get MMS working with Softbank, and people on forums elsewhere say it's worked for them.
dr.m0x said:
Also could be a permissions problem. You need to make sure the permissions for the new file the are same as what's already in the directory.
Click to expand...
Click to collapse
How do I do that? I'm pretty new to all this, two days ago I was Googling where to find my Sensation's settings menu
If you want to ensure the mms.apk has correct permissions you can simply run:
adb shell chmod 644 /system/app/mms.apk
This will set the correct permissions for apps in the /system/app folder, although its worth reading up on linux permissions to understand what the command is actually doing.
Permissions didn't help, but I've managed to track down another Mms.apk file that works well enough - messages don't integrate properly with HTC's Messaging app, but I can send and receive MMS. I'm going to keep looking for a better apk but at least this one functions!
If not, what else is done under the covers?
Also, what are the differences when installing applications
•From the android market
•sideloaded from web download
•sideloaded using adb install
•sideloaded using adb push
I copied this question from another place (I cannot put link here because I am new here) because I also have the same question and want to know more about this.
oldyoungguy said:
If not, what else is done under the covers?
Also, what are the differences when installing applications
•From the android market
•sideloaded from web download
•sideloaded using adb install
•sideloaded using adb push
I copied this question from another place (I cannot put link here because I am new here) because I also have the same question and want to know more about this.
Click to expand...
Click to collapse
Some .Apk's can be placed in system/data/app while others can't , make sure the .apk you're trying to place in system/data/app is supported or you may end up restoring your device. if the apk can run from the system /data/app then yes with the right permissions ...
Apk's from the market will give you detailed info from the apk like permission needed , supported devices ect, even the developers contact info ( in other word they are approved by Google.
while "sideloaded" apk or web apk (not coming from Google) are pirates apk,modified apk ect. who knows what permissions it needs or what info you are sharing with whoever modified the apk...
So be careful what you get into your device and where is placed on your device
Sent from my SPH-M930BST using Tapatalk 2
oldyoungguy said:
If not, what else is done under the covers?
Also, what are the differences when installing applications
•From the android market
•sideloaded from web download
•sideloaded using adb install
•sideloaded using adb push
I copied this question from another place (I cannot put link here because I am new here) because I also have the same question and want to know more about this.
Click to expand...
Click to collapse
Simply placing the apk into the correct folder is not enough. You will also need to set the permissions to the same as the other apps in that folder (I can't remember the permissions off the top of my head). This can easily be done using Root explorer, or using an adb shell and the chmod command.
Play Store installs and sideloaded installs achieve the same result, however you will want to be careful where you download apk files from. Apps from the Play Store are less likely to be malicious in nature, and , of course, you should never be pirating paid apps.
Adb push would not be enough as you would still need to set permissions. Unless you are installing a system app, it is better just to use adb install.
rootedVette said:
Adb push would not be enough as you would still need to set permissions. Unless you are installing a system app, it is better just to use adb install.
Click to expand...
Click to collapse
Are you saying the "adb push" will only copy file into the target location but "adb install" will copy the file into the target location AND also set the proper permission for you?
With all of the usual warnings about the source/safety of "side-loaded" apps aside. . .
I simply put the .apk file onto the SD card (anywhere), and then use a file manager like Astro to "open" it (root access not required). You will be prompted to see if you really wanted to install the app. Then let Android do its thing. The app will be installed where it belongs, with all the permissions it needs.
For this to work, you must first tell the device to allow installation of apps from unknown sources. Go to Settings | Security, and check Unknown Sources.
hi guys i have a .apk file i.e. sectabletplayer.apk from another rom i dont want to mention name. when i tried to install it like a general .apk file it says "Aap not installed" . i googled around alot found ADB injecter it says "installation failed" and reason for this error is "unable to mount system r/w " tried to make custom flashable .zip file the file existed in given path but not installed i mean not running totally useless. can anybody help me out of this?
try to set ON Unknown-Sources in Settings/Security/Device-management
ameya1990 said:
hi guys i have a .apk file i.e. sectabletplayer.apk from another rom i dont want to mention name. when i tried to install it like a general .apk file it says "Aap not installed" . i googled around alot found ADB injecter it says "installation failed" and reason for this error is "unable to mount system r/w " tried to make custom flashable .zip file the file existed in given path but not installed i mean not running totally useless. can anybody help me out of this?
Click to expand...
Click to collapse
First this app will only work on a stock/stock base ROM. Second, you need a root file app, like root explorer or root browser. In root explorer you have to select to give r/w permission.
Go to the location of the app, long press it and select copy. Then navigate back to
/system/app and paste it. Then long press it again, select permissions and make it rw-r--r--. Then reboot
Hopefully this will install for you. If it doesn't than the apk itself would need to be modified.
One last thing, if you have another sec.player.apk in system/app, you might need to change it from .apk to .bak then reboot before you begin the other process. You can just rename it back to
.apk and make sure permissions are right then reboot to re-enable it.
Lies, spewed poetically from galaxy S3!
Hi everyone,
There is a way to find the .apk of apps downloaded from playstore. ull need root and root browser, we will use here esfile explorer. open esfile explorer and press top left-->tools enable root explorer and show hidden files, then go to local-->device now go to file data-->app and thats it, to find system apps u can go to device-->system-->app.
Wiked dudes production
Pull Apk in Non-Rooted Device.
There is no need of a rooted device,
you can pull the apk by using following techniques.
//_______________________________________________________
A) Using ADB
1) Determine the package name of the app, e.g. "com.whatsapp" (WhatsApp).
if you don't know the package name, you have 2 options to get the package name
i) Visit play store and search for the desired application, The link of the app contains the package name. "https://play.google.com/store/apps/details?id=com.whatsapp" (WhatsApp) where com.whatsapp is the package name
ii) use command "adb shell pm list packages" , this will list the package name of all application installed.
2) Once you know the package name, get the apk installed path by using command "adb shell pm path com.whatsapp"
it will return the apk path of the application, like this
package:/data/app/com.whatsapp-2/base.apk
3) Now to pull apk, by using command "adb pull /data/app/com.whatsapp-2/base.apk"
Apk will be extracted to the same folder where adb is present
//_______________________________________________________
B) Using ESFileExplorer
1) Open ESFileExplorer and navigate to User Apps either by (swiping left to right twice) or (goto APP under Library in Navigation Drawer)
2) Select App you want to pull, and click on Share.
3) Share the Apk to another device via Bluetooth or to desktop via AirDroid,
shanrais said:
There is no need of a rooted device,
you can pull the apk by using following techniques.
//_______________________________________________________
A) Using ADB
1) Determine the package name of the app, e.g. "com.whatsapp" (WhatsApp).
if you don't know the package name, you have 2 options to get the package name
i) Visit play store and search for the desired application, The link of the app contains the package name. "https://play.google.com/store/apps/details?id=com.whatsapp" (WhatsApp) where com.whatsapp is the package name
ii) use command "adb shell pm list packages" , this will list the package name of all application installed.
2) Once you know the package name, get the apk installed path by using command "adb shell pm path com.whatsapp"
it will return the apk path of the application, like this
package:/data/app/com.whatsapp-2/base.apk
3) Now to pull apk, by using command "adb pull /data/app/com.whatsapp-2/base.apk"
Apk will be extracted to the same folder where adb is present
//_______________________________________________________
B) Using ESFileExplorer
1) Open ESFileExplorer and navigate to User Apps either by (swiping left to right twice) or (goto APP under Library in Navigation Drawer)
2) Select App you want to pull, and click on Share.
3) Share the Apk to another device via Bluetooth or to desktop via AirDroid,
Click to expand...
Click to collapse
ur right however, not all system apps are present using the second way, and first way is complicated for some people and might confuse them. if someone would want to change something he saw on google, that is connected to system apps or other stuff"like systemui" i think rooting and copying the apk from its directory is best. btw thanks for ur concern about this, believe it or not for the first 7 month i posted this it posted in android wear, and no one was commenting, i made it with the xda app, i think it has alot of bugs.
Lord_of_Death said:
ur right however, not all system apps are present using the second way, and first way is complicated for some people and might confuse them. if someone would want to change something he saw on google, that is connected to system apps or other stuff"like systemui" i think rooting and copying the apk from its directory is best. btw thanks for ur concern about this, believe it or not for the first 7 month i posted this it posted in android wear, and no one was commenting, i made it with the xda app, i think it has alot of bugs.
Click to expand...
Click to collapse
IMO, if one is able to root the phone, then he will certainly not find any complication in pulling apk using first way.
shanrais said:
IMO, if one is able to root the phone, then he will certainly not find any complication in pulling apk using first way.
Click to expand...
Click to collapse
u might be right bro but rooting is only downloading a file and flashing it through odin.