ThePianoGuy

What Is ADB? Android Debug Bridge (adb) is a command line tool that lets you communicate with an emulator or connected Android device. You can find the adb tool in android sdk/platform-tools or Download here Download adb.exe 1.0.36 + fastboot for Windows Revision e02fe72a18c3-android Downloaded from Android SDK. 100% clean and untouched It contains the following files: adb.exe AdbWinApi.dll AdbWinUsbApi.dll fastboot.exe ---------------------------------------------------------------------------------------------------------------------------------- List of commands: -a directs adb to listen on all interfaces for a connection -d directs command to the only connected USB device returns an error if more than one USB device is present. -e directs command to the only running emulator. returns an error if more than one emulator is running. -s <specific device> directs command to the device or emulator with the given serial number or qualifier. Overrides ANDROID_SERIAL environment variable. -p <product name or path> simple product name like 'sooner', or a relative/absolute path to a product out directory like 'out/target/product/sooner'. If -p is not specified, the ANDROID_PRODUCT_OUT environment variable is used, which must be an absolute path. -H Name of adb server host (default: localhost) -P Port of adb server (default: 5037) devices [-l] list all connected devices ('-l' will also list device qualifiers) connect <host>[:<port>] connect to a device via TCP/IP. Port 5555 is used by default if no port number is specified. disconnect [<host>[:<port>]] disconnect from a TCP/IP device. Port 5555 is used by default if no port number is specified. Using this command with no additional arguments will disconnect from all connected TCP/IP devices. ---------------------------------------------------------------------------------------------------------------------------------- Device commands: adb push <local>... <remote> copy files/dirs to device adb pull [-a] <remote>... <local> copy files/dirs from device (-a preserves file timestamp and mode) adb sync [ <directory> ] copy host->device only if changed (-l means list but don't copy) adb shell [-e escape] [-n] [-Tt] [-x] [command] run remote shell command (interactive shell if no command given) (-e: choose escape character, or "none"; default '~') (-n: don't read from stdin) (-T: disable PTY allocation) (-t: force PTY allocation) (-x: disable remote exit codes and stdout/stderr separation) adb emu <command> run emulator console command adb logcat [ <filter-spec> ] View device log adb forward --list list all forward socket connections. the format is a list of lines with the following format: <serial> " " <local> " " <remote> "\n" adb forward <local> <remote> forward socket connections forward specs are one of: * tcp:<port> * localabstract:<unix domain socket name> * localreserved:<unix domain socket name> * localfilesystem:<unix domain socket name> * dev:<character device name> * jdwp:<process pid> (remote only) adb forward --no-rebind <local> <remote> same as 'adb forward <local> <remote>' but fails if <local> is already forwarded adb forward --remove <local> remove a specific forward socket connection adb forward --remove-all remove all forward socket connections adb reverse --list list all reverse socket connections from device adb reverse <remote> <local> reverse socket connections reverse specs are one of: * tcp:<port> * localabstract:<unix domain socket name> * localreserved:<unix domain socket name> * localfilesystem:<unix domain socket name> adb reverse --no-rebind <remote> <local> same as 'adb reverse <remote> <local>' but fails if <remote> is already reversed. adb reverse --remove <remote> remove a specific reversed socket connection adb reverse --remove-all remove all reversed socket connections from device adb jdwp list PIDs of processes hosting a JDWP transport adb install [-lrtsdg] <file> push this package file to the device and install it (-l: forward lock application) (-r: replace existing application) (-t: allow test packages) (-s: install application on sdcard) (-d: allow version code downgrade (debuggable packages only)) (-g: grant all runtime permissions) adb install-multiple [-lrtsdpg] <file...> push this package file to the device and install it (-l: forward lock application) (-r: replace existing application) (-t: allow test packages) (-s: install application on sdcard) (-d: allow version code downgrade (debuggable packages only)) (-p: partial application install) (-g: grant all runtime permissions) adb uninstall [-k] <package> remove this app package from the device ('-k' means keep the data and cache directories) adb bugreport [<zip_file>] return all information from the device that should be included in a bug report. adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>] write an archive of the device's data to <file>. If no -f option is supplied then the data is written to "backup.ab" in the current directory. (-apk|-noapk enable/disable backup of the .apks themselves in the archive; the default is noapk.) (-obb|-noobb enable/disable backup of any installed apk expansion (aka .obb) files associated with each application; the default is noobb.) (-shared|-noshared enable/disable backup of the device's shared storage / SD card contents; the default is noshared.) (-all means to back up all installed applications) (-system|-nosystem toggles whether -all automatically includes system applications; the default is to include system apps) (<packages...> is the list of applications to be backed up. If the -all or -shared flags are passed, then the package list is optional. Applications explicitly given on the command line will be included even if -nosystem would ordinarily cause them to be omitted.) adb restore <file> restore device contents from the <file> backup archive adb disable-verity disable dm-verity checking on USERDEBUG builds adb enable-verity re-enable dm-verity checking on USERDEBUG builds adb keygen <file> generate adb public/private key. The private key is stored in <file>, and the public key is stored in <file>.pub. Any existing files are overwritten. adb help show this help message adb version show version num ---------------------------------------------------------------------------------------------------------------------------------- Scripting: adb wait-for[-<transport>]-<state> wait for device to be in the given state: device, recovery, sideload, or bootloader Transport is: usb, local or any [default=any] adb start-server ensure that there is a server running adb kill-server kill the server if it is running adb get-state prints: offline | bootloader | device adb get-serialno prints: <serial-number> adb get-devpath prints: <device-path> adb remount remounts the /system, /vendor (if present) and /oem (if present) partitions on the device read-write adb reboot [bootloader|recovery] reboots the device, optionally into the bootloader or recovery program. adb reboot sideload reboots the device into the sideload mode in recovery program (adb root required). adb reboot sideload-auto-reboot reboots into the sideload mode, then reboots automatically after the sideload regardless of the result. adb sideload <file> sideloads the given package adb root restarts the adbd daemon with root permissions adb unroot restarts the adbd daemon without root permissions adb usb restarts the adbd daemon listening on USB adb tcpip <port> restarts the adbd daemon listening on TCP on the specified port ---------------------------------------------------------------------------------------------------------------------------------- Networking: adb ppp <tty> [parameters] Run PPP over USB. Note: you should not automatically start a PPP connection. <tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1 [parameters] - Eg. defaultroute debug dump local notty usepeerdns ---------------------------------------------------------------------------------------------------------------------------------- adb sync notes: adb sync [ <directory> ] <localdir> can be interpreted in several ways: - If <directory> is not specified, /system, /vendor (if present), /oem (if present) and /data partitions will be updated. - If it is "system", "vendor", "oem" or "data", only the corresponding partition is updated. ---------------------------------------------------------------------------------------------------------------------------------- Internal debugging: adb reconnect Kick current connection from host side and make it reconnect. adb reconnect device Kick current connection from device side and make it reconnect. ---------------------------------------------------------------------------------------------------------------------------------- Environment variables: ADB_TRACE Print debug information. A comma separated list of the following values 1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp ANDROID_SERIAL The serial number to connect to. -s takes priority over this if given. ANDROID_LOG_TAGS When used with the logcat option, only these debug tags are printed.

i'm in

i need one

i'm in

This tutorial will learn you how to remove Google Ads and other ads from any APK (app), the ads are a specific part in the source code that can be removed easily without damaging the app. I'm using the app Tubemate as an example 1. Backup the app from your device or download the official apk from apkpure.com that you are looking for. 2. Download APK Easy Tool. 3. Open APK Easy Tool, setup the paths, select an APK and decompile the APK file 4. Open decompiled directory. Navigate to Tubemate-2.2.9.blahblah.apk -> smali -> com. 5. Delete the following ads folders - adsdk - inmobi - lifestreet - millennialmedia - mocoplex - mopub - smaato - tapit DO NOT delete the folowing!!! - a - b - c - google 6. Open "google" folder and delete "ads" folder 7. Navigate to android -> gms and delete "ads" folder 8. Go back to the root folder of decompiled apk. Open "assets" folder and delete "adlib" and "mmadsdk" folder 9. Recompile the APK and enjoy Note: This method may not work on some apps Credit: AndnixSH - broodplank1337 (His method of removing Google ads folder)

Why unsigned APK, and why is it recommended for most games? With an unsigned APK, you can install the APK over the original. You can login with your Google+ account without signature error, and login with your Facebook account without uninstalling Facebook app. No more login not working complains! What are the difference between unsigned APK and signed APK? Unsigned APK is an APK that was been modded but the modders kept the original signature by developer to make Google login working. SIgned APK is an APK which was been re-signed by modders with APKtool's signature, dated 29-02-2008. Google or other social medias may not work due to signature that was been changed. You can only install an unsigned APK on your rooted device because it require the signature to be disabled using Lucky Patcher. If your phone is not rooted, please saerch on Google about how to root your phone. Note from Xtreme Myst: By using the method described, consider to NOT add new files or remove existing files on the APK. For example, along with your mod you need to add a file into the APK, let say in "assets/myfile.dat". It won't work and lead to failure during APK installation. Another example, let say you've successfully remove XC protection and been thinking it's okay to pull the "lib/armeabi/libxigncode.so" out of the APK. Again, it causing installation failure. This is because all file structures in the APK was mapped and their info was stored in "META-INF/CERT. SF" file. The solution is you need to put all your mods along with expected APK file structures in the compiled APK, sign it (with any desired key), then pull the "META-INF/CERT.SF" from this newly signed APK to be used as replacement for the old one at your working APK. Let's start modding. First, we need to change another apps. 7zip or Winrar 1. Right click on the APK file -> Open With -Z Choose Another App 2. Click on "More apps" and tick "Always use this app to open .APK files" 3. Click "Look for another app on this PC" 4. To go program files and select any program to open with APK. I'd recommended 7zip or Winrar 5. The program will open 6. Drag and replace the modded file in the .APK file That's it. You are done Smali and XML modding If you were modding Smali or XML and you have recompiled it and signed it, you can do it 1. Compile the APK (Resigning an APK is optional) 2. Drag and replace a modded file from a signed APK to an original APK, and the APK will become an unsigned APK. 3. Simply close the program, and you are done! Replace signatures in META-INF (Second method) You can delete the modified signatures and add the original signatures in META-INF folder but it may not work for some apps 1. Open signed APK 2. Open META-INF folder 3. Delete all signatures and add original signatures by game developer in META-INF folder. This will make APK into unsigned APK Credit: AndnixSH

nulling all the banned function. delete all opcodes except "ret"

GameGuardian is the best

https://lh3.googleusercontent.com/ts0dooMDSGGBMvBKw2nBH1__E-sJH10MsOIOPqX4OhUDZJ6cU7MewTsNU7RXpuI9Ba4=w300-rw Modern Strike Online - VER. 1.14 Playstore Link: https://play.google.com/store/apps/details?id=com.gamedevltd.modernstrike&hl=en Hacks: 1. Ammo size increased (not unlimited) 2. Medkit always activated 3. Grenade always activated 4. Anti-ban (untested) 5. God mode How to install signed APK (non-root/root): Google login will NOT work! 1. Uninstall official game version 2. Open this site on your device and click the download link 3. Open the Download app on your device or open any file manager app and go to /Sdcard/Downloads/ and tap the APK file 4. Click install to install the modded APK 5. Download OBB file, extract it, and copy the OBB folder to /Android/obb 6. Run the game How to install unsigned APK (rooted devices): Google login will work! 1.PATCH THE SIGNATURE FIRST 2. Backup your savedata by login with your Google account 3. Open this site on your device and download the file 4. Open the Download app on your device or open any file manager app and go to /Sdcard/Downloads/ and tap the APK file 5. Install modded APK over the original game 6. Download OBB file, extract it, and copy the OBB folder to /Android/obb 7. Run the game Download: [Hidden Content] Credit: AndnixSH

Can't login with your Google+ on modded games? Really need to uninstall Facebook? NO PROBLEM. i will show you how to patch signature and make your device thinking that the signature is always true, so you can install any UNSIGNED modded apk on What can you do after patching? - Install Unsigned APK - Install Unsigned APK over the original APK - Login with your Facebook account without uninstalling Facebook app - Login with your Google+ on modded games 1. Make sure your device is rooted, and have latest SuperSU and Busybox binaries. 2. Download Lucky Patcher from http://lucky-patcher.netbew.com/and install it DO NOT DOWNLOAD LUCKY PATCHER FROM PLAYSTORE 3. Open Lucky Patcher from the app drawer and let it refresh 4. Click "Toolbox" 5. Click "Patch to android" 6. Check "Signature Verification status always true" and "Disable .apk Signature Verfication" and click Apply IMPORTANT! If Lucky Patcher does not allow you to check "only patch dalvik-cache, which means, your device does not support patching dalvik-cache. When you patch signature verifications without patching dalvik-cache, the dalvik-cache will be cleared and it will take 5-10 to boot once. "only patch dalvik-cache" is the quickest way to patch the signature verifications. JUST PATCH IT ANYWAY IF DALVIK-CACHE PATCH IS NOT SUPPORTED AND STOP ASKING QUESTIONS! Most devices running Android Lollipop will reboot when patching 7. You will get a message saying that the patches are applied (ONLY if patched in dalvik-cache) 8. Reboot your device 9. Install the unsigned modded apk over the playstore version. (Do NOT uninstall the playstore version!) 10. Open the game, login to Google Play, and enjoy! Credits: AndnixSH (for creating this tutorial) ChelpuS (for creating Lucky Patcher ) Raxx (for grammar fix)

thanks

i want more CoC accounts

nice. would like to try this

ok

they will probarly ban my IP-address. My parents can use free US VPN when it expired

i want more coc account

i have Zenmate VPN premium but it will expire in 5 days and it is too expensive, so i would like to have this yearly account

isn't it ad-free?

I always remove bloatwares from all of my devices.

cool

there is no limitation of value in x86 so you don't have to think about MOV R0, R7 thing 99,999,999 value is mov eax, 0x5f5e0ff = b8 ff e0 f5 05 max value is 0xffffffff = 4,294,967,295 , but it if max value is 2,147,384,687 for some games, the value will go negative or the game will crash mov eax, 0xffffffff = b8 ff ff ff ff i'm unsure if it works

Modded Game Name: The Sandbox Evolution Google Play Store Link: https://play.google.com/store/apps/details?id=com.pixowl.tsb2&hl=en Rooted Device: Not Required. Mod Features: - All elements unlocked Hack Download Link: [Hidden Content] Installation Instructions (non-root): Step 1: Download the signed Modded APK file above using your favorite browser or a download manager of your choice. Step 2: Copy the file over to your Android device via USB or wirelessly. Skip this step if you're using your Android device to download the mod. Step 3: Browse to the location where the hacked APK is stored using a file manager of your choice. Step 4: Tap on the .APK file then tap 'Install' and the installation should begin. Step 5a: If the mod contains an OBB file, extract it if it's archived and copy the folder to /Android/obb. Step 5b: If the mod contains a DATA file/folder, extract it if it's archived and copy the folder to /Android/data. Step 6: Once the installation is complete, everything should be ready. Enjoy! Note: Make sure you have enabled 'Unknown Sources' in settings before installing the Modded APK. If you encounter issues, our Frequently Asked Questions topic may help you. Installation Instructions (root): Step 1: Patch the signature using Lucky Patcher. CLICK HERE! Step 2: Download and Install the unsigned APK over the original game Step 3: Once the installation is complete, everything should be ready. Enjoy! Credits: AndnixSH Mod Video/Screenshots: N/A

Have "ptrace: Operation not permitted" error when you try to debug a game using GDB? Follow these steps "PID" stands for Process ID The game is EDEN Avalon Legends (th.co.tdp.eden). Turn off the Advanced Task Killer app, if it is running. Open the game, and press the HOME button to minimize the game. Type dumpsys meminfo to view all running processes. Take note of the number next to "pid" (PID stands for "Process ID" and changes everytime a process starts). In my example, I'll take note of the number "383". Now, using the PID you just noted, type: This will give a list of clones of the main PID and depending on the game, can attach to it regardless of if ptrace is denying the main process id (PID), if that makes sense. Attach to a clone of the process gdb -pid xxxxx Example: gdb -pid 4546 The symbols are loaded which means the game is debugged Dump as normal with gcore gcore /sdcard/DUMPEDFILE Do not worry about any warnings like these you may read in the Terminal app: Extract the DLL file as normal with cracked Winhex Proof: But EDEN Avalon Legends will not run if you replace the modded DLL file, due to crc32 check. Note: Games such as GrandChase M doesnt work. Even the clones found through "ls -l" still deny ptrace it basically depends on the securty the game has but its good info and you never know what seems a really hard game might just work as did avalon legends which like 4 i know are trying to bypass ptrace for Credits: Antiklor (For helping me with ptrace bypass) AndnixSH

Downgraded to 3.7.0.0 and everything works

Droid4X have a lot of bugs and customer support are poor so i avoid it