Develop Bugs

How can you install APKs from other ROMs?

I have looked around quite a bit, and haven't really figured out the straight answer on this.
I have seen apks that can be downloaded of things like the clock or gallery app, and then I have seen custom roms that include things like the AOSP dialer, contact app, browser, etc. However in my small amount of trying, I couldn't install them on top of another ROM (or stock).
Is there an issue with signing them, or does it have to be done in recovery mode, or do I have to remove the existing stuff in something like Titanium backup and then install the other APKs, or would my only option be to learn the dark arts of rom cooking?
Edit: Answered thanks to mrchu001. Doing an "adb remount" and then issuing the install command from the shell worked.

I'm not sure if this works for ALL apks between roms, but when i flashed Fresh it didn't have the cooliris 3d gallery that DC has, so i opened the zip, and copied the APK from one rom to the other then flashed it. I'm sure there are some programs that just won't work even if you did it this way, but something to consider.

That works in most cases..
Just get the zip on your computer, open it extract the apk you want and adb install it to your connected device.

No luck with either method mentioned above. I'm sure I don't know what I'm doing... but I did an adb install <apk name> and got an error:
Code:
MacBook: tools laydros$ adb install CarDock.apk
1344 KB/s (238640 bytes in 0.173s)
pkg: /data/local/tmp/CarDock.apk
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
And I grabbed one of the base rooted roms, unzipped, added the CarDock and DeskClock apks to the system/app folder with everything else, and the ROM failed to load. I did the same clockwork rom manager install rom from SD card methods I have done before. I assume this means that the zip was not properly signed.
The apks I was testing were ones from bugless beast 0.4, any ideas?

laydros said:
No luck with either method mentioned above. I'm sure I don't know what I'm doing... but I did an adb install <apk name> and got an error:
Code:
MacBook: tools laydros$ adb install CarDock.apk
1344 KB/s (238640 bytes in 0.173s)
pkg: /data/local/tmp/CarDock.apk
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
Click to expand...
Click to collapse
it looks like you didnt direct your terminal correctly. i'm assuming you have the sdk on your computer btw. now try to upload the rom you want on your phone. plug it in. make sure usb debugging is set. make sure the apks you want to put on your phone are on your desktop. and try this:
Code:
cd ~/*where every your sdk is*/tools
./adb remount
./adb shell
./adb install ~/desktop/*apk name* /system/app
./adb shell reboot

maybe you already tried but just incase.. do you have the Unknown sources check box "Checked" under "Settings/application" menu? if not you need to to install apps not from the market..

mrchu001 said:
it looks like you didnt direct your terminal correctly. i'm assuming you have the sdk on your computer btw. now try to upload the rom you want on your phone. plug it in. make sure usb debugging is set. make sure the apks you want to put on your phone are on your desktop. and try this:
Code:
cd ~/*where every your sdk is*/tools
./adb remount
./adb shell
./adb install ~/desktop/*apk name* /system/app
./adb shell reboot
Click to expand...
Click to collapse
The remount part did it, and then doing the install from adb shell. Thanks so much.
For the sake of anyone else that finds this, once you type adb shell, you are working from the phones shell instead of the one on your computer, so you would skip that command. I ended up moving the files to the sdcard, and then doing
Code:
cd ~/*where every your sdk is*/tools
./adb remount
./adb shell
(at this point you are at the phone's prompt)
install /sdcard/*apk name* /system/app
exit
(now you are back at the computer's prompt)
./adb shell reboot
Now I need to figure out what to install to get the phone/contacts working. Calendar and Mms applications were easy, but after installing several apks for the phone and contacts I just have a mess.

FroydVillain 1.0.0 install *.apk files in /system/app
Hi has anyone tried installing another apk file in FroydVillain 1.0. I follow the steps in the thread described i am able to issue adb shell commands and i have placed the apk files in the SD card as described. but i am getting an error as below that the file or dir is not found. tried several paths:
# install /mnt/sdcard/*.apk /system/app
install /mnt/sdcard/*.apk /system/app
install: can't stat '/mnt/sdcard/*.apk': No such file or directory
# install /sdcard/*.apk /system/app
install /sdcard/*.apk /system/app
install: can't stat '/sdcard/*.apk': No such file or directory
I use /mnt/sdcard path cause on Froyo the SDCARD folder is under /mnt.
any help solving this. i am trying to install some of the HTC Sense UI app to sys app. Like Stock.apk for test. and HTCAlbum.apk and others same result every time.
I have tried also AndroidCommander 0.7.9.6 updated for froyo. installing with it's install option button, and also from the console i run the shell command for install, successfully adds the apk in sys app folder but the apk is not installed, and asks for installation.
Thanks.
Regards Alek

help
Hi,
Can you explain to begginers (like me) how do you installed the apk in system/app? please, I want to install contacs.apk form CM9 to other rom.
Thanks.

[Q] How do you change system font without rooting?

Okay, so i have been at this for like an hour and its pissing me off, cuz i just keep going in circles....i was using this tutorial
http://www.tech-recipes.com/rx/10573/android-how-to-change-the-default-system-font-requires-root-or-adb/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+Tech-RecipesMain+(Tech-Recipes+Main) and when ever i typed adb remount it told me remount failed: Operation not permitted

I checked the post and he says the following
Manual Way Using ADB and Command Line
1. This way assumes you have the Android SDK installed and setup. You also need the USB Debugging drivers for your device installed. Also be sure to copy the TrueType font file into the same folder as the adb.exe and fastboot.exe programs (default is c:\android-sdk-windows\tools ). This should work on a non-rooted device since we are using the SDK and ADB Remount commands; however, I have not tested personally on a non-rooted phone.
He said should but he has not tested it. Considering you are trying to replace something in /system I doubt it will work without root.

[Q] Cannot Access ADB shell on android SDK or remount filesystem as r/w

I am pretty new to this whole android market. I have a stock epic 4g running DI18 and 2.1 update 1, rooted with the one-clicked root available on the sticky note forum[forum.xda-developers.com/showthread.php?t=770388]. It installed superuser and Clockwork Recovery mod 2.5 and i have been able to access that with no problem, even did a system backup. i tried using the remount/unmount feature in this and it read that the filesystem was unmounted and mounted, but i could not figure out how that could operate with the root tools application, because i have to reboot the system and it still reads the same problems. I am not looking to change roms just yet because the SQL benchmark test scores are 49.4 seconds which seem to be enough for me. I am however trying to change the themes, boot animation, and move the cache to SD card. I have downloaded the SetCPU, titanium backup with the available BusyBox in help menu, and Root Tools by Jrummy16. The root tools application works to manage applications, but anytime i try to use any "tweaks or hacks" such as ad blocker, it does not allow it and shows me a screen reading, "unable to remount filesystem read/write." To fix this problem i downloaded android SDK on my windows 32 bit system, and downloaded all of the neccesary drivers. Most of the instructions tell you to access the Command Prompt on the computer and use:
cd\
cd androidsdk\tools
adb devices
The problem is.. once i get the file to read C:\androidSDK\tools, i try to enther adb devices and it reads to me that " 'adb' is not recognized as an internal or external command, operable program or batch file"
I am just trying to get my root tools to work so i can manage my cache and use the ad blocker, and possibly install new roms later. i also tried using the 'su' command and it said it was not recognized.
Few questions:
Is there any steps i missed to be able to develop and change my themes, or is there anything i should have used instead of the programs i used?
Is there a different way to access adb shell on the epic 4g?
Is there another way to change themes/fonts/widgets/scroll animations?

hookinhorns81 said:
I am pretty new to this whole android market. I have a stock epic 4g running DI18 and 2.1 update 1, rooted with the one-clicked root available on the sticky note forum[forum.xda-developers.com/showthread.php?t=770388]. It installed superuser and Clockwork Recovery mod 2.5 and i have been able to access that with no problem, even did a system backup. i tried using the remount/unmount feature in this and it read that the filesystem was unmounted and mounted, but i could not figure out how that could operate with the root tools application, because i have to reboot the system and it still reads the same problems. I am not looking to change roms just yet because the SQL benchmark test scores are 49.4 seconds which seem to be enough for me. I am however trying to change the themes, boot animation, and move the cache to SD card. I have downloaded the SetCPU, titanium backup with the available BusyBox in help menu, and Root Tools by Jrummy16. The root tools application works to manage applications, but anytime i try to use any "tweaks or hacks" such as ad blocker, it does not allow it and shows me a screen reading, "unable to remount filesystem read/write." To fix this problem i downloaded android SDK on my windows 32 bit system, and downloaded all of the neccesary drivers. Most of the instructions tell you to access the Command Prompt on the computer and use:
cd\
cd androidsdk\tools
adb devices
The problem is.. once i get the file to read C:\androidSDK\tools, i try to enther adb devices and it reads to me that " 'adb' is not recognized as an internal or external command, operable program or batch file"
I am just trying to get my root tools to work so i can manage my cache and use the ad blocker, and possibly install new roms later. i also tried using the 'su' command and it said it was not recognized.
Few questions:
Is there any steps i missed to be able to develop and change my themes, or is there anything i should have used instead of the programs i used?
Is there a different way to access adb shell on the epic 4g?
Is there another way to change themes/fonts/widgets/scroll animations?
Click to expand...
Click to collapse
I'm not sure if you had a typo in your original post or if that is how you actually entered the commands on your computer when you tried this, but based on the "paths" you entered, the commands should be:
CD\
CD\androidsdk\tools
adb devices
As for the themes, fonts, etc., there is an app in the market called MetaMorph that will do that for you. You just need to have .zips for it to apply.
There is also a tutorial for MetaMorph "somewhere" in the "Themes" section on XDA. I couldn't find a link to post for you, but I know it's there!

As far as getting in adb if you have windows XP you can go to the tools folder and hold shift and right click it. In the.menu it will say start command prompt here. Click it. Now you are on your tools folder where adb is. Then you can use adb and get into the shell.
Sent From My Evo Killer!

can not mount system in read-write mode using adb without recovery mode

I wanted to change my device model, so I copied build.prop from another mobile to my mobile. I am already rooted. But unfortunately I did not change the o.s. from gingerbread to froyo in build.prop ( I have android 2.2 FROYO) When I rebooted, there were many errors. It is now showing no sim card. Mobile network search gives error. Effectively, I can not use the mobile. Terminal emulator, X-plore etc. stopped working. Only Rom toolkit free version works and astro file manager works. Other programs are forcefully closed. Needles to say, I must replace new build.prop with new one.
Using adb I can only pull files but can not write as it is in read only mode.
adb root and adb remount works only if you are in recovery mode ? Y mobile does not have any custom recovery so when I boot in recovery mode it hangs.
Superuser has installed su in system\bin directory. But from adb shell I can use su also. It gives permission denied error. Hence I can not remount the system.
I have read similar threads and found that on some mobiles adb root or adb shell su works but on some not.
I am using Vista 32 bit with admin rights, still can not use root in adb.
Please tell me, how can I mount system read-write. I can not install root explore as google play and even internet is not working.
Please help.

maheshchavan said:
Using adb I can only pull files but can not write as it is in read only mode.
Click to expand...
Click to collapse
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop

ruscan.calin said:
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
Click to expand...
Click to collapse
OMG ruscan.calin i COULD KISS YOU! I had tried to change my OG EVO 4G's buildprop file to another phone so that I could purchase & download an incompatible Google Play app. However after I restarted the phone wouldn't start! It would boot into my rooted HTC EVO 4G Android 2.3.3 and HTC Sense 2.1 but it would get stuck on the wallpaper with just the notification bar at the top and all buttons would be frozen. However I noticed when I plugged in my phone to my computer via usb the computer recognized it. I always keep my phone with USB debugging enabled so I thought I should be good right? I have spent the last 4 hours trying to install and setup adb with no real previous experience with it. I am familiar with dos from years ago and that helped me as it's basic procedure, commands, etc. Then I found out how to install the HTC drivers which I needed and then download the Android SDK with adb that's included which many guides show easily. I started the command prompt (cmd), typed my adb devices command and hurray it showed my phone! I connected and quickly navigated to the build.prop system folder! Luckily when I changed the file I made a bak backup and left it in the same folder. Now the main issue was figuring out how to change the naming of the files which I did via usual adb commands (mv build.prop.bak build.prop). But then to no avail I couldn't get it to write due to it being a system read only folder! Arg! Then I found your post on here, above, and typed it in simply leaving out the adb push portion and replacing that with the mv file command instead and first changing the name of the bad file and then replacing the bak file as the good copy! I exited back to the adb main and unplugged my phone. Moment of truth and man was everything flashing through my head at once! I booted up and YESSSSSSSSSSSSSS, it worked! I went back into root explorer and got rid of the offending leftovers and I've learned my lesson! I just don't want to think about what would have happened if I hadn't found this post. Thank you and if anyone else makes this hug mistake let me know and maybe I can help. Moral of the story don't mess with the build.prop or any system folder unless you know what you're doing! Thanks again!
Quick Guide to Fix Android "build.prop" Issues:
1. Find and download USB drivers for your phone by model or type (HTC EVO 4G's HTC Fastboot drivers): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
2. Download and install Android SDK and choose adb: http://developer.android.com/sdk/index.html
Guide: http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
3. Run a command prompt from the "c:/program files/android/android-sdk/platform-tools/" directory. I had to copy the command prompt to get it to open there but sometimes a right-click action will do it. The guide below will help just navigate down to "Using ADB" and skip the rest.
Guide: http://www.howtogeek.com/114667/how...y-default-move-almost-any-app-to-the-sd-card/
4. Once you open the command prompt and you're in the "c:/program files/android/android-sdk/platform-tools/" foler type "adb devices" and your device should appear. If it does move on to next step.
5. Then type adb shell and use the ls command to see directories. Then you'll need to navigate to the system folder by typing "cd system" and then type "ls" to look around in the directory (similar to "dir" in DOS). You should now see the bad build.prop file.
6. You'll need to rename the file or push a correct version. First you need to use the "adb shell" command again and then "su" and finally "mount -o rw,remount /dev/block/mmcblk0p1 /system" to make the directory writable (see ruscan.calin post above for additional info).
Note: I only had to rename my build.prop as I already had my old one in the same system folder. You may have to copy the bad build.prop to your computer, edit it and then push it back to the same system directory. These directions are only for renaming files in the same folder. For the info on how to copy the file to your computer and push it back to your phone go to step *10 below or use the guide below it.
7. I already had the bad build.prop in the system directory with my old one which I had named build.prop.bak. If you have this too simply rename by changing the name first of the bad file to anything by typing "mv build.prop build.prop.bad" or similar.
8. Next rename the build.prop.bak to build.prop by typing "mv build.prop.bak build.prop". Everything should go smoothly and move onto the next step.
9. Finally, If no error messages are found, simply type "adb reboot" or "adb shell reboot" (Depending which version of ADB you have). You should be done, your phone will reboot like normal (working, lol) and everything should be working again! YAY!
*10. To copy the build.prop to your phone type "adb pull /system/build.prop c:\" and the file should be placed in the main c:/ directory on your computer. Navigate to the root (c:/) directory and then right click and "open with" the "build.prop" file using a notepad or other file editor. Then use the text editor (Notepad, etc) to change back what you originally changed to mess everything up. There is tons of stuff on the net to let you know what to fill back in depending on your phone model/type. Or it's possible to get a previous version from an old Nandroid backup or similar. Save the changed text file and make sure its named the same "build.prop" and make sure it's still in the root directory (If you're having issues on this step or just want more insight check out the guides and threads below for more help).
Guide 1: http://androidforums.com/admire-all...p-computer-not-phone-using-root-explorer.html
Guide 2: http://www.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
Guide 3: http://forums.androidcentral.com/sp...-replaced-build-prop-phone-wont-start-up.html
*11. We've already made the directory writable in step 6 so we simply need to push the file back to the phone. If any error message appear re-do step 6 to make writable again. Otherwise push the modified file back to the phone by typing "adb push c:\build.prop /system/". Back to step 9 above! Yay!
If anyone wants to help cleanup this quick guide or make any changes feel free. I just wanted something so that if anyone else has this issue they won't have to worry or search forever to find a solution. OMG it's 2:30AM, to bed... I ride! LOL
Enjoy,
5th :highfive:

THANK YOU!!! Totally saved me today.
One thing that I noticed. After pushing the correct build.prop, I had to fully power down, then turn back on my Razr for it to load up the fixed build.prop.

error message,Help please
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?

jigarpattani said:
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
Click to expand...
Click to collapse
What step are you on? What phone do you have? More info please?

i am have problem whit my pantech flex i need to use the build.prop.bak but when i type the su it stay in blank do nothing any ideas pls help

ehy there hope someone can help me...i have an archos 97b platinum, messed up with build.prop. So i pulled out and restored but can't push in any way. I have a cwm installed, tablet rooted but i alwais got "permission denied" at push command. Other error is operation not permitted" if i try remount command from adb. i can do mount -o rw,remount /dev/block/mtdblock7 /system but after that push still give me permission denied.
any suggestion?
http://imgur.com/FDLp4fl
i open a 2nd cmd, give the mount -o rw,remount /dev/block/mtdblock7 /system , and system is now rw, but from the first cmd when i give "push build.prop /system (or /system/build.prop) it will always return me permission denied
help

dev.block
i want to view to dev/block using adb shell #
eg . what block is boot.img
what block is recovery.img
what block is system.img
what block is cache.ing
adb shell getprop mtd is not work . Pls Help Me & sent to mail [email protected]

[Q] Kindle Fire (D01400) soft-brick

Hi all.
Yesterday, a friend of mine asked me if i know about tablets with android os, i told him that I know a little, and he challenged me to try to fix his daughter's kindle stuck at load screen (the one with colored triangles).
I accepted the challenge and started to research at forums about Kindle Fires stuck, i will resume my problem ....
I downloaded Firekit for linux (iḿ using Ubuntu 12.04) and started to try some commands. I got ADB console to connect on the device using
Code:
# adb shell
command, and started to run around the system inside the Kindle.
For some reason (noob nonsense action), I remounted /system partition as RW and ran (again, not knowing the side effects of that) the command wipe and chose ALL. Yes, i got the system folder cleaned and now i can't run commands on kindle console. I still can
Code:
#adb push
things inside the device. I'm not planning to buy a factory cable or build one, and, here is my question, is there a way to copy these binary files inside the /system folder again, without factory cable? Is there a place where i can find these binaries for download or a package containing them?
About the device: Kindle Fire (D01400)
Bootloader: Stock (Kindle fire logo)
Fastboot: Can't find compatible devices.
Rooted: Maybe (i got root logidn on command adb shell)
Thank you for helping.

Ok, I downloaded the Stock ROM from amazon and uploaded /system folder using adb.
Code:
#adb shell
now working, i got again kindle console as root but i couldn't find ls or rm on /system/bin and now, all environment variables are unset. Maybe a problem with home path (i'm logged as root).
any advice how to reset the root user's home?
Code:
# export
ANDROID_ASSETS
ANDROID_BOOTLOGO
ANDROID_CACHE
ANDROID_DATA
ANDROID_PROPERTY_WORKSPACE
ANDROID_ROOT
ASEC_MOUNTPOINT
BOOTCLASSPATH
DOWNLOAD_CACHE
EXTERNAL_STORAGE
LD_LIBRARY_PATH
LOOP_MOUNTPOINT
PATH
PWD
TERM
TERMINFO