HZCK's APK Tool
I have made a little APK Uninstall/Install Application.
It's very easy to use, use the command prompt to uninstall or install.
This setup has ADB & Fastboot in the setup, so you can use ADB or FASTBOOT too.
Current existing commands:
1. apk-cmds / Check commands.
2. apk-install / Install a APK File.
3. apk-uninstall / Uninstall a Application.
It's very easy to install it, just run the setup and it installs it for you.
This setup has a KEY, i just made one to protect it.
KEY: 8PT6M-EEC51-LZKKU-IGV4E
IF KEY DOESN'T WORK: 8A2IT-2UCCA-LL5LX-IU4R0
If you want to uninstall only HZCK's APK Tools, type the command
apk-setupuninstall
[ ! ] A INFORMATION ABOUT THE UNINSTALLER!
I dont know if you use the uninstaller, that it deletes the complete
System32, please remove this not automatic. If you test it and it doens't remove
data from System32, please tell it in the comments.
Download Links
Dropbrox (Translated License / Untranslated License)
Mediafire (Untranslated License)
Google Drive (Translated License)
Why does this have a license key?
Related
Hello
This will be my first tutorial on rooting a galaxy player 5.0 using Ubuntu 12. please let me know if there are some changes you believe needs to be made. i will also update this document with photos and add a second part for flashing a custom ROM. i have it as an attachment as well as copied into this post.
Root and Flash Galaxy Player 5.0 (linux)
Hello after some searching I deiced to learn how to root and flash my Galaxy Player 5.0 loaded with GingerBread (2.6.35-Kernal, 2.3.5-firmware).
**First we need to prep your player**
1) go to settings
2) now to applications
3) now open development
4) finally check the USB debugging box
**Install needed Apps**
5) download and install terminal emulator
**Install android SDK**
6) open terminal and use the command (adb) we are looking for “Android debug bridge”
1) if you get android bridge move to step 3 if you do not get android bridge move to step 2
7) adb= Android SDK
1) open terminal and use type sudo apt-get install eclipse-jdt allow the install to complete
2) now lets install the android sdk using this link android-sdk
3) use the software defaults allow it to complete the install process
4) open the eclips application
1) go to help → install new software click add end enter this URL //dl-ssl.google.com/android/eclipse/
2) check the available boxes and choose next followed by finish (restart eclips)
3) now click window → preferences choose browse locate your android SDK folder
4) Apply → OK
5) now choose window → SDK manager
1) select all the packages you will be working with (I choose 4.0.3 and above)
**Lets Root your Player**
8) plug your micro USB into player and Linux box
9) download the following files rootme files //papousek.org/downloads/galaxy_player/rootme.tar.gz
10) extract the file to your home dir
11) open terminal and use the following command
1) cd root/
2) chmod +x rootme.sh
3) ./rootme.sh
12) this will take a few mintutes let the program run **you will know the process is done when your player reboots**
**Lets check if your player is Rooted**
13) open the terminal emultaor you installed on your player
14) in the command line enter the following command
1) su
2) enter
15) you should get a “Allow super user box” choose allow
16) in the terminal emulator type
1) you should see a $ symbol
2) type su
3) you should now see a # symbol this means you are root.
I rooted mine using Oneclick Root. Version 2.2.2.It took less than 5 minutes. My player has the 2.3.5 stock firmware.
TUTORIAL ON ADB AND LOGCAT : JDMC : Just doing my contribution.
This is part of TeamAscend, so if you are going to post this Tutorial on other forums please credit me, visit our website : I AM AWESOME!
Hello this is just to teach newbie users on how to install adb and get it working, I will also teach you how to use logcat to help devs with particular issues, okay lets get into it, I will try to be as formal and understandable is I can, I'm still a 15 year old so bare with my written language, not that its bad but we Kiwi's use weird slangs...
Setting up ADB
1. Okay first of all we need to enable Android debugging.
1a. To do so, head into Settings > development and check android debugging, If you're on CM10 + you will need to set Developer Options to "ON" then select Android Debugging.
2. Get a usb adapter and connect it to your pc and connect your device. Let it install drivers "If it's the first time.
3. Download "SDK Tools". and install it to your desktop for now, you can move it later when you want.
4. Now create a new folder on the desktop and copy all SDK contents into it so its neat and tidy.
5. Open "SDK Manager" and un-check everything except "Android SDK Platform-Tools" and click install packages, wait till it's done then close the window, now you should be in the folder that contains the SDK Tools etc... if you see the "platform-tools" folder you're good to go.
6. Now open the "platform-tools" folder and copy the destination output at the top.
7. Now we need to set the new destination to CMD, click the start button type "cmd".
8. When it opens type "cd" obviously without the ", now hit space and click paste now your command should look something like this...
"cd C:\Users\Your PC name\Desktop\the folder that contains the sdk tools name\platform-tools" here's mine : "cd C:\Users\Lenovo\Desktop\ADB\platform-tools". Now hit enter, your target folder will change.
9. Once its done type " adb devices", make sure your phone is connected! now hit enter and it'll show your device, now you know ADB Is up and running! If doesn't show your device continue to the next step, if it does continue from step "11".
10. Download the HTC drivers and install it, plug your phone again and wait for it to install all components, if MTP fails to install just ignore it. (If your storage is on MTP), now repeat the procedure from "7" again.
11. Now lets Logcat, Now there are 2 different approaches to the logcat, I will be showing you how to do both in this tutorial. Neither one is more correct than the other, it is 100% personal preference. Feel free to try both and see where you get.
LOGCAT PROCEDURE
Doing logcat from inside the CMD window.
1. Make sure your phone is plugged in and debugging is on, now repeat procedure "7" to set target folder if it isn't already done. ie : cd _____________________________ <-- your folder destination.
2. Type "adb logcat" without the " and hit enter. It will then print a list of random writing, whether you understand or not, it doesn't matter, it's not for your use .
3. To save the logcat for devs to use, once the logcat is running, please RECREATE the bug/issue you are having. so that it logs the error into it, now to stop the logcat hit "ctrl" + "C".
4. Once this is done please RIGHT CLICK choose "Select All" then press "Enter" on your keyboard this will copy the entire log to the clipboard. You can then paste it into a .txt file to upload and show to devs.
Doing logcat to text file.
1. Now repeat procedure "7" to set target folder if it isn't already done, make sure your phone is plugged in and usb debugging mode is enabled. Once this is done we are going to type the following command "adb logcat > logcat.txt" without the ", this should initiate the logcat, it will appear as though nothing is happening, this is correct!!! So don't worry.
2. Once the logcat is running, please RECREATE the bug/issue you are having. To stop the logcat on your keyboard press "ctrl" + "C".
3. Now you've done logging, note the logcat.txt file will be located in the platform-tools folder, just open it and you will see logcat.txt, upload it for the dev and he/she will investigate.
More ADB Commands for various logcats Thanks to "Tcpaulh" from Modaco.
External adb folder, just needed thanks man : Download
1. radio logcat for Wifi issues.
adb logcat -b radio > radiolog.txt
2. kernel logs.
adb shell
su
cat /proc/kmsg > /sdcard/kmsg.txt
exit
adb pull /sdcard/kmsg.txt
3. kernel message buffer (on request).
adb shell
dmesg > /sdcard/dmesg.txt
exit
adb pull /sdcard/dmesg.txt
This was a tutorial I wrote up for my old device, users found it easier to understand then most, I cleaned this one up a bit which should be suitable for the Desire X, note, I may ask allot of question like a noob on the Q & A but HTC is so confusing.
Hopefully, users start using this so we can help out our devs, our sweet sweet devs, so they can whip u some magic.
If this helped, hit the thanks meter, no need for donations.
I wasn't paying attention to what I was doing after updating some apps, and froze some some application that is necessary, now my CATS60 will not boot. The app likely just uses the disable or hide command, but I am not sure what I misclicked, so I need to get a list or currently disabled apps or reenable all apps. I entered TWRP recovery, mounted all partitions, and connected through ADB shell.
This is what I get when I try to find out what's enabled/disabled:
Code:
# pm list packages
CANNOT LINK EXECUTABLE: library "libqc-opt.so" not found
page record for 0x7fb1658010 was not found (block_size=64)
adbd is running as root, and the file does exist:
Code:
~ # find / -name 'libqc-opt.so'
/system/vendor/lib/libqc-opt.so
/system/vendor/lib64/libqc-opt.so
I am using TWRP as recovery, and recovering system, data, and boot from backup does not fix this.
Does anyone know either
How can I make pm command work from recovery?
Where is the list of disabled apps stored, so I can manually edit it?
Thank you.
I found the list as used by the app (com.ramdroid.appquarantine), and it appears I blocked Google Calendar. However I have not found any way to "unfreeze" the app through recovery, this is simply a tracking file the app uses, not the actual enable/disable for Google Calendar.
Setting PATH and LD_LIBRARY_PATH environment variables does not help. Running it from inside the folder containing libqc-opt.so causes it to fail on a different external link.
Copying it to a second file called pm2, opening in vi and adding exports gets me as far as:
Code:
CANNOT LINK EXECUTABLE: cannot locate symbol "__android_log_close" referenced by "/system/lib64/libandroid_runtime.so"
Is it possible to chroot inside adb, and what do I need to mount first in order to do so? I don't know enough about Android to know which parts of the system I actually need.
Hey guys.
On my old SM-J730G device, some ROMs did not have the confirmation dialog for ADB certificates. This prevented me from connecting to the shell, getting logcat output, etc.
To resolve, I needed to copy the certificate to the device, install a root file manager, and copy the file to / data / misc / adb / adb_keys.
Well, I developed an application that helps in this process. Your requirements are only to have the device rooted and to have copied the adbkey.pub file to the device. The app will assist in the implementation of the same.
Download: https://play.google.com/store/apps/details?id=com.gobrito.adb_keys
Screenshots on Play Store page
Created with Flutter
NOTE: if you are in the wrong area, I ask you to move the topic to the correct area, and sorry for the inconvenience, this is my first topic.
In the spirit of removing stubborn pre-installed APKs from freshly unpacked Android devices, I would like to share the apps I removed using adb and the commands used to do so.
I personally do not use Office or Bing so these were my primary targets, but I also removed OneDrive, OneNote, Outlook and Edge as well.
This is step-by-step for Windows users:
1. Download platform-tools from https://dl.google.com/android/repository/platform-tools-latest-windows.zip
2. Extract to C:\ (or a place of your choosing)
3. Open a command prompt from your start menu by typing "cmd" in your Windows search bar.
4. You should see something like: C:\Users\YourUsername_>
5. Type "cd C:\platform-tools" and press Return/Enter
6. You should now see C:\platform-tools>
7. Plug in your device with a USB cable and ensure you have turned Developer Options on your device (search Google for how to do this if unsure)
8. Type "adb shell" and you should get an Unauthorized message in the command prompt window followed by a pop-up on your device asking if you trust the computer you are connected to.
9. Select the option to trust the computer you are connected to.
10. Type adb shell again and hit Enter/Return and you should see a unique alpha-numeric device ID show in the command prompt now.
11. Begin uninstalling the packages you wish to no longer be stuck on your Surface Duo 2 with the command below.
12. Repeat the command below for each package/app you wish to uninstall.
pm uninstall --user 0 <package name from the list below goes here>
(Below are the packages I have personally removed line by line and still have stable experience on the device. Most are evident in the package name of what was removed. I will update the list as I remove more.)
com.microsoft.amp.apps.bingnews
com.microsoft.office.officelens
com.microsoft.skydrive
com.microsoft.amp.apps.bingnews.overlay.duo2
com.microsoft.office.onenote
com.microsoft.bing
com.microsoft.office.outlook
com.microsoft.office.officehubrow
com.microsoft.surface.office.outlook.overlay.duo2
com.microsoft.surface.tips
com.microsoft.bing.overlay.duo2
com.microsoft.surface.onedrive.overlay.duo2
com.microsoft.teams
com.microsoft.todos
com.microsoft.emmx (Edge Browser)
com.microsoft.windowsintune.companyportal
Hi. Somewhat cautious of doing anything that bricks my Duo 2 - I use many of the Microsoft apps, so I'm more interested in removing the Google suite of apps. Does the above approach work for Google apps too?