Database Info

[Q] installing busybox - pushing files to droid

Hello,
I started experimenting with my Android yesterday when I found out about metamorph which requires rooted phone and busybox..
I managed to root the phone but couldnt install the busybox with the application from the market - it says that busybox was not found..
Then I installed the SDK platform, and wanted to do it with adb
I downloaded busybox ... tar.bz2 file and unrared it into SDK/tools and tried pushing it to my android to /system/local by doing:
adb push /Users/../android/platform-tools/busybox /data/local
but adb pushed the subfolders (children) to the /data/local folder instead of the folder with childen folders itself.
Now I wonder:
1. how to remove all those junk files?
2. am I doing the right thing? should I copy the tar.bz2 without unraring it? what is the right procedure?
is there any easier way to accomplish this?
Thanks for help

One way to get busybox is with titanium backup. Install the app open then menu*problems*Yes, do it.

jerrycycle said:
One way to get busybox is with titanium backup. Install the app open then menu*problems*Yes, do it.
Click to expand...
Click to collapse
This wont work with my telephone - HTC Desire

[GUIDE] Merging updated system apps with old one, GET MORE FREE MEMORY!!

(Preface for noobs : /system and /data are two different partitions. Freeying up /system won't get you more intrenal memory, but /data does. Old apks rest in /system and updated versions placed in /data. You can replace the old apks using newer versions)
I heared Titanium Backup PRO does something like, but you can do this with any File Explorer with ROOT access. Its works 100% for Android Gingerbread 2.3.x , try on other versions.
### Do it on your own risk, I am not responsible for anything ###
1. Update the desired app to the latest version from Google Play Store
2. Open File Manager, Enable ROOT_ACCESS, remount /System as writable
3. Goto /system/app and backup the desired apk to sdcard
4. Goto /data/app and copy updated apk
5. Paste into /System/app
6. Note down the filename of old apk and delete the old apk
7. Rename the new apk into the old filename
8. You may encounter a FORCE CLOSE if the app was running in background
9. The updated apk in /data/app will be removed automatically
10.Restart your device, Done!
I replaced Playstore, Maps, Google Search ect..
Example: For PlayStore, updated apk will be com.android.vending-1.apk, and old apk is vending.apk
Hit thanks it it works, Thanks

thanks, nice guide! All is ok (PlayStore, Terminal Emulator), but if I merge last version of "Google Play Service", then Gmail or Maps shows the message "Unknown issue with Google Play services" when I open them... do you know how to solve? thanks in advance
p.s. configuration in signature

Better use Link2SD. It makes the integration of updates into system seamless. Rebooting the device is optional (restart only if you encounter errors).

thank you for your suggestion! I tried TitaniumBackup but it gives me the same error, then now I'm trying with Link2sd and it works well, BUT the new apk file is in system/app instead of system/priv-app, and its name is "com.google.android.gms-1.apk" instead of "PrebuiltGmsCore.apk"... can this create some problems in future?
EDIT: I tried moving to the priv-app folder and renaming the apk to be identical as before and it seems to work... for now...

It's the package name, it won't create any problems. There is no need to rename the app to match the old one. Default location when converting to system app is in /system/app. I don't know if you can change the location, but you can move it manually to /system/priv-app thru root explorer. Just restart the device afterwards to eliminate FC errors.

how to find apks on my device

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.

Accidentally uninstalled a pre-installed app? Here's how you get it back.

Some apps (such as Huawei Health) are installed on your device during the initial boot. They can, however, be uninstalled, and there's no obvious way to get them back.
Here's how you do it!
The APKs live in the /cust directory on your device. You can either pull them (using ADB, e.g. 'adb pull /cust/preinstalled/public/app/') or use a file explorer app to browse to the same directory and click the APK you want to install.
Author (paulobrien)
Original post
https://community.hihonor.com/docs/DOC-1244

Systemizing user app forcing boot into recovery?

I'm trying to convert an app to a system app by placing it in /system/system/priv-app. I'm rooted using Magisk, but otherwise running completely stock Pie, with stock recovery installed. Here's what I've tried:
1. Using Magisk's Terminal App Systemizer module. This was the first approach I tried.
2. Using ES File Explorer to move the folder and change permissions.
3. Using Link2SD to make app into a system app.
4. Booting into TWRP using Fastboot, then using TWRP's File Manager to move the app into the /priv-app folder and set permissions.
5. Following the directions here to place the .apk directly into the root of the priv-app folder.
6. Following the directions here to make a folder for the app inside of /priv-app through adb shell and placing the .apk inside that folder.
Each time I've done this, when I try and reboot my phone it hangs during the boot sequence on the G logo with a little loading bar at the bottom. After a little while, the phone will automatically reboot into recovery and prompt me to either do a factory reset or try again (trying again causes a bootloop). I can boot back into the bootloader using the hardware keys and use fastboot to get TWRP running. From there, if I delete the .apk inside the /priv-app folder my phone will boot as normal. Note that I've had to sideload the OTA image when I used Magisk/Link2SD to systemize the app, as I couldn't find the app inside the /priv-app folder at all.
I've tried 2 different APKs with the same result. I make sure to set the proper permissions before rebooting, but it would appear that I'm doing something wrong with the .apk, since the problem goes away as soon as I delete it from the /priv-app folder.
Any help? What am I doing wrong?