contract killer trainer and cheat | android games

This is a good app but unfortunately its the only one of its kind that I've found for hacking games on Android systems and can be used for all games. before There is a new Trainer / Cheat App on Android Market it's called "Contract K. Trainer". It gives you unlimited money, credits, all weapons and more. and now no available on the market.

note:

there are four points to consider in gamecih2.
first, the input number on the gamecih2
second, the default number (the numbers will be changed),
third, the numbers has changed on the games,
Fourth, if you use gamecih2, use the airplane mode, or you gamecih2, became lite version. ( lite version = click the bottom advertisement to enable Hidden Mode. Wait 7 seconds on the page ( after stop loading the page ), and press your hotkey. If "Browser" is in red, you are in Hidden mode. If not, try again by closin out of GameCIH and try again )

code for contract killer android games 

money = easy guy, have try...

energy = 007f73b8

XP total = 007f0388 or 008a78a0

your XP = 00f20bdc

credit = 013b2908 or 013d0724

 How to use:

1. Start GameCIH ( for xperia play I use old version 2.1.1 because 2.2.1 and 2.2.2 is a lite version ) and select the button / hotkey you want to use to activate GameCIH (personally I use the search key button on my xplay).

2. Starting the game.

3. click on the selected button ( search hard  key button )

4. box to select the Input Number, enter the number of such money or anything that you need to change it, which you have now in the game.

5. there are many lines, close the window of the program by selected back button.

6. spend money in the game, or vice versa, we obtain, so would the number of money (or anything else) has changed. ( remember that input number has changed or trainer fail )

7. Again we go in the gamecih app, now we have again press the Input Number, enter the number has changed (for example, have the money 3000, bought something, money was suppose 2600, then enter 2600)

8. the program finds the values that has changed, select the value (s) and change such as 99999 ( don't put so much number or will crash ), confirm, go to the game by selected back button.

9. if this time you're in luck, then the number will change to something that you have written.

and done

download via market     gamecih 2.1.1     gamecih 2.2.1        gamecih 2.2.2

Tutorial move applications to SD Card with out rooting

run out of space from your ROM? it's usually problem for midle range of android phone. that build of cheap hardwares, naturally isn't? What should we do so we do not run out of phone memory? sell it and replace with a better way? it's not the best answer if we only have limited funds. we need to do is to move the applications that have been installed in the internal memory to SD card. but the way that is usually done by most people, require rooting in the device, which can of course remove the warranty. but this does not require rooting in our device.

I realise there are a few threads about this, but I thought I would make a new one for my easier guide, and hopefully people will find it more easily as they won't have to scroll through pages of other threads to find an answer.
I am now successfully running most apps from my SD Card now. I just thought I would make an easier guide as the others are fairly complex for noobs like me. So here is my guide - hope it helps.

following instructions:

1. Download the android SDK here

2. Extract using something like WinRar

3. Copy the second folder into the sdk named "android-sdk-windows" to the desktop.

4. Open the folder on the desktop and open the file, SDK Manager.exe (as no such file as setup.exe exists in the new version of the SDk)

5. Close the command / windows command prompt window that opens

6. Untick all options you are promted to download except ones like the manuals, and Essentially, ensure the USB driver option is selected / ticked.

7. Let these files download

8. Ensure on your phone, USB Debugging is on - Go to Settings/Applications/Development/USB Debugging and ensure its ticked / on.

9. Download and install HTC Sync from HTC's website for your device.

10. Connect your phone by USB and select the HTC sync option when it pops up with charge only, disk mode etc.

11. Allow the sync to complete.

12. Open windows command promt. Start / Run

13. Type in (without quotations) "cmd"

14. The following should appear. (with your user account instead of William - note its "users" in windows 7, not documents and settings

15. Type in the following after the ">" at each step (without quotations,and including spaces and capital letters)

"cd desktop\android-sdk-windows\tools" (might be "cd desktop\android-sdk-windows\platform-tools" in windows 7)
"adb devices"
"adb shell"
A $ sign should pop up
"pm setInstallLocation 2"
Another $ should pop up

And your done. Close everything, disconnect phone, turn off phone and then turn it back on again.

16. Now the phone will be set to install all apps you install onto the SD card. However, current apps on phone will mostly still be stored on the internal memory. This process doesn't move these apps for you, it adds the ability. So you must now manually move those already installed on the phone.

To do this, go to settings / applications / manage applications
Then you just click on an app, and the move to SD card box should no longer be Grey. So you must now move all the apps you want onto the SD Card.


Note:
I would not advise moving apps like widgets, or anything system related. Furthermore, for example, I have the 3g watchdog app constantly running, so it is advisable to keep apps like that on the internal memory.
See below for more information on widgets.

If you get an invalid path message, it suggests it cannot find the required folder you are asking it to. My method only works if you have saved it to the desktop. If you have saved it elsewhere it won't work. You would have to redirect the desktop part of the code ("cd desktop\android-sdk-windows\tools") to somewhere else.

For example if you saved it in my docs instead, it would be - "cd My Documents\android-sdk-windows\tools". That's why I used the desktop, it's far easier to code the cmd to find the file.

Finally, part of the problem is that when you extract the core sdk rar file, it is extracted to a folder wherever it was saved originally titled android-sdk-windows, but in that is another folder called android-sdk-windows, and then only once you open that second folder do you gain access to the tools, usb driver folders and so on. Therefore, you must either, remove the first folder so you are left with just a folder named android-sdk-windows which inside contains tools., or you must recode my above to say "cd Desktop\android-sdk-windows\android-sdk-windows\tools".

Likewise, beware as I can't remember for certain, but I think the sdk in its core form is called android-sdk_r07-windows or something (08/09 too), so rename this to android-sdk-windows.

One final note. Fairly irrelevant to this process but since this is being viewed a lot I'll say it anyway. Don't ever use a task killer. Wrecks the phone! Happened to me, happened to thousands.

fix widget

Just to clarify about widgets for anyone unclear. There seems to be a bit of confusion here. This may have been said earlier I don't know, but again hopefully this is simpler. Ill add this to the first post too.

With this process, you can still use widgets, but not if they are on the SD Card (which they automatically will be assuming you got my original guide process to work.) Ive tested this, and it works every time for me. I know some widgets are weird but I think it will work. So to get a working widget.

Note:
Some irritating widgets may require you to uninstall the app before you proceed to step 1.

1. Download and install the widget from the android market
2. Go to Settings/Applications/Manage applications/Downloaded (or All) and find/select your widget.
3. Select move to phone.
4. Turn off the phone
5. Turn on the phone
6. Widget should now work.


option two

you may use softwares called SIMPLE2EXT

S2E works only with CyanogenMod7!
The application install a script, that allows you to move applications and some cache in sd-ext partition and back. In application can specify what needs to be moved.

Application is translated into: English and Russian. If you want to translate the application into your native language, I'm waiting for your requests to pull on GitHub =)

Support moving to sd-ext:
1. App and Private app
2. Applications data
3. Dalvik and download cache
Support mounting sd-ext as ext4

REQUIREMENTS

Device runned under CyanogenMod7
Second partition on SD card formated as ext3 or ext4
(You can do this via ROM Manager or Recovery)

USAGE
Install S2E
Choose what items will be moved to /sd-ex
Reboot (first boot may take a long time)

tutorial rooting with z4root

z4root is the standard ROOT applications for Android, basically running this application on the device for ROOT. Applications need to be rooting Superuser to function properly, to install it before installing z4root Superuser also this.
Analogues: Superuser similar to the Windows User Account Control (UAC) which prevents a program to change the operating system or setting a windows system by providing access rights to User2 ID who you defined in advance (To help protect your computer, you can create a user account standards for all users who share a computer. so when someone who has a standard account tries to install software, Windows will prompt the administrator account password so that a software can not be installed without the knowledge and permission of the account / user ID tSB),
and z4root as a tool that gives an account / ID UAC admin rights on the page, so that other programs can change settings on an operating system.

It is an app you install from the market or by side loading, that has a single button that will root your device.

How safe is this?

Should be 100% safe - nothing on disk is changed besides the root binaries, so if something goes wrong, simply rebooting the device should fix up any and all issues. Here is the list so far of known compatible and incompatible devices for the permanent root option. 
Compatible with PERMANENT root option

Samsung Galaxy S (All variants)
Backflip
Sony X10
Xperia Mini
Droid 2
Galaxy Tab
Galaxy I5700
Galaxy 3 I5800
Droid X
Samsung Acclaim
Cricket Huawei Ascend
Motorola Cliq
Huawei 8120
Hero
G1
Optimus T
Droid 1
Garmin Asus A50
Motorola Defy
LG Ally
Motorola Flipside
Motorola Milestone 2
Dell streak
X10 Mini Pro
Smartq v7 android 2.1

Incompatible with PERMANENT root option

Desire (requires nand unlock)
Desire HD (requires nand unlock)
Magic (unknown)
Evo (requires nand unlock)
G2 (requires nand unlock)
Archos 70 (unknown)
myTouch 3G (unknown)
Wildfire
Droid Incredible

First download z4root here, then save on your mobile phone.

check the option Unknown Sources at the check in settings -> Application settings

open z4root apk file, and then install.

open z4root, select Permanent Root.

Rooting process will be conducted by z4root. Let your mobile phone for several minutes until you restart your phone. If you freeze for more than 5 minutes, do not worry, unplug your battery, then repeat root process again. 

tutorial overclocking CPU for android

tutorial overclocking CPU for android

step:
1. Download the required files  link1   TASS_OC.7z
2. Extract TASS_OC.7z
3. Run the application S5570 Odin Multi Downloader
4. Click the button and select the file TASS_v1.0.ops OPS
5. Click the PDA and select the file CODE_S5570DXKA8_REV02_OC.tar.md5
6. Turn on device to Download Mode (Center Key + Power + Vol Down key)
7. When it detect in Odin, click the Start button
8. Wait until the flashing process is complete and install the SetCPU application.

tutorial video overclocking CPU for android

DO AT YOUR OWN RISK

totorial unrooting on android

UNROOTING INSTRUCTIONS:

Unfortunately, the method to unroot by clicking on the Unroot button in Superoneclick does not work. So follow the following steps to unroot.

1. Download rootexplorer.apk and install Root Explorer on phone.
2. Run Root Explorer. A 'Superuser Request' prompt will come up. Press Allow.
3. Now, on the top, there will be a button saying 'Mount R/W'. Press it. It should change to 'Mount R/O'. The button should say 'Mount R/O' in order for you to be able to do anything in the following steps.
4. Now scroll to the bottom, click on system. Then click on bin.
5. In the bin folder, look for a file named 'su'. Long press on this file, and select Delete to delete it.
6. Now go back to the system folder by pressing the Back button once.
7. Now enter the app folder. Scroll down and look for the file named 'superuser.apk'. Long press on this file and delete it.
8. Exit Root Explorer after this. Uninstall it if you don't want to use it.
9. That's it. Your phone will be un-rooted.

Another method to unroot 1

1. Download and install Terminal Emulator.
2. Run Terminal Emulator on the phone. If you don't see a keyboard to type, press Menu and press Toggle Soft Keyboard.
3. Type su and press enter. Press Allow on the 'Superuser Request' prompt. The $ sign will change to a #.
4. Now type the following line exactly as it is and press enter: mount -o rw,remount /dev/block/mtdblock3 /system
5. Nothing will happen visually. The pointer will shift to a new line.
6. Now type the following line and press enter: rm /system/bin/su
7. Again, type following line and press enter: rm /system/app/superuser.apk.
8. Now exit Terminal Emulator. Your phone is un-rooted.

Another method to unroot 2

1. Format the Micro SD Card to FAT32.
2. Copy the DREAIMG.nbh file to the Micro SD Card. (NOT A ZIP FILE)
3. With the phone off, hold camera and press power to boot into the bootloader.
4. Once the bootloader is loaded, press power to install.
5. Press the trackball to continue and press talk + menu + power to reboot.

and this would flash the image to the phone that was there when the rooting hole was discovered. then you would from there to Root or UnRoot by selecting different files to get you back to last ver for either rooted or unrooted.

tutorial App2SD + Move2SD Enabler

The next method if using application App2SD (need root access) inadequate (less internal memory). we will use Move2SD Enabler for each installation .apk can be set automatically in order to move all to the SD memory card (External). So applications that previously could not be transferred to the SD card because it does not yet support the storage to the SD, could be moved even though there are few applications that really make a rule can not be moved (phone only). This method can save the use of internal memory. there is a shortage of this method, if we connect to a PC using USB Storage mode, then the application is moved to SD, can not run (Force Close).

tutorial Totally Move applications to SD card.

1. Root your device first. tutorial how to rooting here.  
2. donload move2SD enabler link1  link2  link3
3. extrack move2SD enabler and install.
4. restart the device.
5. open move2sd enabler. tap I've read it > next.
6. will appear like this: select external > apply.

now, when you install applications will be installed on the SD card.

note:
1. what about the applications already installed ?
go to settings > applications > set the application > applications that want to tap on the move.

2. do not move all applications to the SD card, the application should always be running in background, for example launcher, keyboard pro, handcent remains in internal memory.

3. to avoid the force close (use applications that are already on the move to SD card) must wear a high speed SD card, such as SDHC class 4 and above.

about app2SD

app2SD

This be the most common method used. In Froyo actually install. Apk can already stored on the SD card, with notes on applications that are installed on the SD card storage support. The transfer was done manually by going to the application App2SD. but there are also applications that will remain stored in internal memory.

App2SD + Move2SD Enabler  (tutorial how to use here)

The next method if using application App2SD (need root access) inadequate (less internal memory). we will use Move2SD Enabler for each installation. apk can be set automatically in order to move all to the SD memory card (External). So applications that previously could not be transferred to the SD card because it does not yet support the storage to the SD, could be moved even though there are few applications that really make a rule can not be moved (PHONE ONLY). This method can save the use of internal memory. there is a shortage of this method, if we connect to a PC using USB Storage mode, then the application is moved to SD, can not run (Force Close).

Virtual Memory (tutorial how to use here)

This method is used if it were less satisfied with the results App2SD, and Move2SD Enabler. This method is actually similar to App2SD + Move2SD Enabler, only the applications and data stored on the ext2 partition that was made before. Almost all. Apk and its data will be stored in the ext2 partition, since this partition will be read as the internal memory by your android device. So although later connected to a PC using USB Storage mode, applications that have entered the ext2, will keep running.

JIT Compiler

Before the official Froyo announcement at I/O, we’d learned that an Adobe employee’s phone was running at ridiculously high speeds. Most outlets quickly chalked this up to the possibility that Google implemented a Just-In-Time compiler for their Dalvik Virtual Machine.
Sure enough, they confirmed our suspicions at the keynote in San Francisco, and we even got a taste of real-world performance (there’s no “theoretical” performance hikes here, folks). We know what JIT does, but I’m sure there are a lot of non-developers out there that can’t understand how it’s able to provide the huge bump in performance for Dalvik.

Technical lead for Android’s Dalvik team – Dan Bornstein – signed in with a blog post over at the Android developers site going into a bit more details about what’s really going on beneath the hood to significantly improve performance of Android (in certain cases) without needing to touch the hardware. Thankfully, he puts it in plain English so you can get – at the least – a pretty basic understanding of what’s going on. Head over there now if you want to learn more about what makes your Froyo so sweet.

Linux-Swap

What is SWAP?
Swap space is an auxiliary storage, such as a portion of a hard-disk, which can be used as memory by the operating system when system RAM is insufficient. This is especially useful on systems with very little system RAM, such as most DD-WRT compatible routers, as it helps prevent the system from running out of memory when multiple background processes are installed.

The difference between Froyo A2SD, A2SD and A2SD+

One of the glories of using Android is having an SD card for storage rather than having internal-only memory. Thanks to Android’s Linux blood, you can even harness the power of the SD card beyond its usual file storage capabilities. On Android, your internal memory is precious and you do not want to install games and applications – especially those which are up to 50MB in sizes – on your internal memory just to make your phone run slower. Instead, you can install the applications on SD card and let your phone take care of the system apps instead, saving more internal memory and speeding up your phone.

The Partitions

Android natively supports fat32 partition. However, thanks to the Android community, support for swap and ext partitions can be enabled too. Depending on the ROM, some can support up to ext4, while others support up to ext3. The explanation about the differences between these partitions is indeed very lengthy and not part of our chapter today. What is important to know, is that Android has support for fat32, swap, ext2, ext3, and ext4 partition support.

Your SD card is by default formatted to fat32. In order to use swap and ext partitions, you need to repartition your SD card. There are several ways to do this, but the most common way is by using a custom recovery installed on your phone (ClockworkMod or AmonRA recovery). Swap is virtual memory which uses extra space on your SD card for virtual memory. However, since Android already has DalvikVM, swap is not really needed. I myself don’t use swap space on my SD partitions. Ext partition is extended partition which was the first ever type of partition created specifically for Linux. It is based of the standard UNIX file system and was designed to overcome the limitations of Minix file systems. Ext 2 is second extended partition, ext3 is third extended partition and ext4 is the fourth extended partition respectively.

Dalvik Virtual Machine

One of the best functions of Android has to be the Dalvik cache. Dalvik cache is a wonder from the point your Android starts up, runs, hibernates and all the way till you device shuts down. Dalvik cache collects the information about the installed applications and frameworks, and organizes them into a writeable cache. Under this writeable cache, it stores the “optimized” bytecode of the applications which is used by the applications themselves later for a smoother operation. This dalvik cache can grow immensely huge as more applications are installed on your phone. It is safe to wipe dalvik-cache. It will be rebuilt again when the phone boots. This also explains why your phone takes ages to start up for the first time. As for my Nexus One, having about 145 applications installed, it takes about 13 minutes to build the cache.

If you ever extract an APK installer file, you will always find a file named classes.dex. This is the file Dalvik finds to build the cache. What makes the process slow? APK is an archive (which is why you can open it up with an unarchiver such as WinRAR or 7-Zip). Being an archive, it provides limited write access to the files contained within and the fact that archives are compressed. Not to forget, APKs are encrypted archives too. Therefore, DalvikVM has to extract the classes.dex files and build the Dalvik table accordingly which makes it easier to write data on it too. With this collective set of data, the Android OS no longer needs to index the applications and find their classes.dex when the phone is already running. Instead, it will just look into one place, and will know what to do next. Nifty huh?

To know what is going on inside the Dalvik VM, you can read about it here.

Froyo A2SD (F-A2SD)

When Froyo was released to Android community, one of its new features was the A2SD implementation. F-A2SD uses fat32 partition natively for application storage. This means, all you have to do is just slot in your SD card and its all ready to go. There is no need to partition the SD card whatsoever. This was a great effort from Google to include A2SD to the Android OS as it gives you an option to choose which applications you want to move to SD card, and which you want to leave on internal memory – BUT – with a condition! If the application developer decides to protect his application and not include A2SD support, you would not be able to move it to SD card. One major problem that F-A2SD has is that it only uses fat32 partition. This way, when the SD card is mounted to the computer, the applications become inaccessible. Not only that, if the applications have widget support, the widgets are removed too when the SD card is mounted. This can become rather a hassle especially if you have to mount your computer several times in a day.

A2SD

The A2SD method is much more interesting. It harnesses the glory of ext partitions. This way, the applications (protected or non-protected), will all be installed on the SD card ext partition. The good thing about ext partition is that when you mount your SD card, the ext partition is NOT mounted together. This said, when your SD card is mounted, the applications will still be accessible and separated from the files and folders on your fat32 partition. On A2SD, the dalvik cache resides on the phone memory.

A2SD+

A2SD+ takes the A2SD one step further. Its pretty useless to have a 512MB A2SD capacity if your dalvik cache is still on phone memory and you have lots of applications installed. This is because the dalvik cache can become pretty huge and just by using HALF of your A2SD’s ext partition, your internal memory can become FULL because of dalvik. Therefore, in A2SD+, the dalvik cache is also moved to SD card. This way, your internal memory is free as a highway. However, remember that Dalvik cache is accessed very frequently. If you have a slow SD card, the overall performance might be affected. I recommend using a class 6 or class 10 SD card for the purpose.

Extreme App2SD / virtual memory A2SD + (tutorial how to use here)

This is the most extreme methods for all installations. Apk, Dalvik-cache, data system & app folder will be moved all the ext2 partition. SD cards are very risky if you are still low speed, because the device will capture all process of the SD card.

note :

If you use virtual memory, app2SD and move2SD enabler, it will take some internal memory, because most of the data for fixed applications installed into the internal memory. we can be sure that: INTERNAL memory will be reduced. If you want all applications into external memory, must use extreme app2SD script. With the consequences of many complaints when the application is installed then the performance of your Android device will be much reduced.