• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Mikfroyo 4.5-Rom Problems installing from...

C

Cool Cake

Lurker
...the Removed Apps folder (on the SD card),
For the life of me, I cant get them to install even when I paste them into /system/app. I use Root explorer to move them.
Any suggestions?
 
Have you tried just long pressing the apk file you want to install and see if install is on the menu that comes up?
 
pressing to install works 90% of the time but some apks have to be pushed.

I have always wondered if it was a permissions issue but there aren't any of those apk's that I even care about
 
Thanks I'll try the long press.

Mr. Ed, could you explain what it means to"push" an app? I thought it meant to copy a program to the /system/app folder and then run it from there.
 
If you push it to system/app/ you'll need to make the permissions match and then reboot the phone to get it to show up...by make permissions match i mean check another app in the system/app/ folder long press, permissions, see what they are then set permission on the file you are placing there, long press, permissions

You can always zip them up and sign them and flash it...btw have you guys seen the drag and drop signing tool over on xda?

usually r/w for user, r for group, r for others...

Edit: SHit i should mention that you will want to rename or move the file thats in there if you are replacing a system app in case you need to go back. I keep a sdcard/backup/apps folder and put all my apk and lib.so files i may want later. Wont matter to you right now since you arent replacing a system app but it should be noted
 
QUOTE=evomattnc;2502598]Ah its called zip signer and its from regaw, good stuff[/QUOTE]

Here is a total Nub question. What is the purpose of a signed file. The above application has like 3 options. Which is best?
 
Apologies cool cake that was sort of an aside.

In short though, all applications must be signed, the system will not install an apk that is not signed. That being said it will allow self signed certificates. When developing apps you can have an app unsigned and work with it in an emulator but to run on an android system you must sign it. More for developing than anything. If you want to learn more about developing check out source.android.com and developer.android.com.

Im not sure which three options you are referring to...its drag and drop...you mean to download it? I havent dl'ed in a while, what are the options?

How did the push go?
 
Just in case you're confused, here is kind of a summary of how you install certain things:

1) From the market - apps automatically install after downloading, and install to /data/app.
2) Sideloaded - tap on an apk using any file manager, and it will prompt you to install it. The app must be signed (as those removed are) before it will install (verifies file integrity). Apps installed this way will go to /data/app, and is only meant for apps that haven't been installed yet, where the apk exists on your sdcard.
3) System apps - Basically, the app drawer will show apps found in /data/app, /data/app-private, and /system/app. Some of those apps that were removed are system apps, and must go to /system/app. When you try the sideloading method, it tries to put them in /data/app. Sometimes that works, sometimes it doesn't. If it needs to go to /system/app, you have to copy it there manually. Really, there is no difference between this and sideloading, other than the destination of the apk. When you sideload (app goes to /data/app), it's just copying the apk there (with a few exceptions). So, once you have the app in /system/app, you don't select it to install. It's already been installed at that point.

The thing is, there are many methods of installing (we call it pushing) apps to /system/app. Sometimes you can just copy it there using root explorer, but permissions can get messed up. If you copy it, reboot, and the app isn't there, you have a problem. If that is the case, adb will work (not the easiest thing to set up) or pushing it via an update script from recovery will work. If it comes to that, just ask, and someone can make one for you.
 
akazabam said:
Just in case you're confused, here is kind of a summary of how you install certain things:

1) From the market - apps automatically install after downloading, and install to /data/app.
2) Sideloaded - tap on an apk using any file manager, and it will prompt you to install it. The app must be signed (as those removed are) before it will install (verifies file integrity). Apps installed this way will go to /data/app, and is only meant for apps that haven't been installed yet, where the apk exists on your sdcard.
3) System apps - Basically, the app drawer will show apps found in /data/app, /data/app-private, and /system/app. Some of those apps that were removed are system apps, and must go to /system/app. When you try the sideloading method, it tries to put them in /data/app. Sometimes that works, sometimes it doesn't. If it needs to go to /system/app, you have to copy it there manually. Really, there is no difference between this and sideloading, other than the destination of the apk. When you sideload (app goes to /data/app), it's just copying the apk there (with a few exceptions). So, once you have the app in /system/app, you don't select it to install. It's already been installed at that point.

The thing is, there are many methods of installing (we call it pushing) apps to /system/app. Sometimes you can just copy it there using root explorer, but permissions can get messed up. If you copy it, reboot, and the app isn't there, you have a problem. If that is the case, adb will work (not the easiest thing to set up) or pushing it via an update script from recovery will work. If it comes to that, just ask, and someone can make one for you.
Click to expand...

Sweet! thanks akasabam. That helps a lot.
 
evomattnc said:
If you push it to system/app/ you'll need to make the permissions match and then reboot the phone to get it to show up...by make permissions match i mean check another app in the system/app/ folder long press, permissions, see what they are then set permission on the file you are placing there, long press, permissions

You can always zip them up and sign them and flash it...btw have you guys seen the drag and drop signing tool over on xda?

usually r/w for user, r for group, r for others...

Edit: SHit i should mention that you will want to rename or move the file thats in there if you are replacing a system app in case you need to go back. I keep a sdcard/backup/apps folder and put all my apk and lib.so files i may want later. Wont matter to you right now since you arent replacing a system app but it should be noted
Click to expand...

Hey EvoMattNc,
The permissions thing worked like a charm. Thank you so much for helping out. All the advice in this thread is going to be remembered for future use.
thanks again
 
You must log in or register to reply here.
Back
Top Bottom