Friday, May 31, 2013




Monday, May 27, 2013

Spy your Girlfriends with Bosspy

If you want to install the software version, please uninstall the previous version of the software currently present on the phone *.

1. Activate your phone and follow the instructions below: go Menu then Browser

2. Then, connect to Internet from your mobile and enter the URL of the site:




3. Wait a few minutes during the download and then click 1mole_xx.apk file to start installing the software on your mobile.

4. Once the installation process is complete. Go to Settings->Accessibility and turn on the Services with the name is "".

5. At google search bar, type in access code to open the software 1mole (default is 123456 ) Or you can dial the access code to open the software 1mole.


6. In 1mole main screen, enter the email address and the password for your account Bosspy and click Login.


7. Click Settings to go to setting screen if you want to change configuration.

8. You can then set the range of updated GPS positions or turn off some options. You can change the secret code used to open the software on the phone. You must format it as follows: # at the beginning of the code and * at the end. For example #345456*

9. After make all change you want, don’t forget click Save and Start to save all new setting and program begin to work.

10. Click Back to return to main screen and then click Exit to hide program interface.

11. You can now log into your account on the website Go to Settings page and config your smtp email account. And then you just need to wait a few hours to receive your first keylogger report.

Eset Smart security 6 May - Jun

Username                             Password                                 Date

Sunday, May 19, 2013

Ten basic Android terminal commands you should know

command line 

For a lot of us, the fact that we can plug our Android phone or tablet into our computer and interact with it is a big plus. Besides the times when we've broken something and need to fix it, there are plenty of reasons why an advanced Android user would want to talk to his or her device. To do that, you need to have a few tools and know a few commands.

 That's what we're going to talk about today. Granted, this won't be the end-all be-all discussion of adb commands, but there are 10 basic commands everyone should know if they plan to get down and dirty with the command line.

The tools are easy. If you're a Mac or Linux user, you'll want to install the SDK as explained at the Android developers site. It's not hard, and you don't have the whole driver mess that Windows users do. Follow the directions and get things set up while I talk to the Windows using folks for a minute.
If you're using Windows, things are easier and harder at the same time.

The tools themselves are the easy part. Download this file. Open the zip file and you'll see a folder named android-tools. Drag that folder somewhere easy to get to. Next, visit the manufacturers page for your device and install the adb and fastboot drivers for Windows. You'll need this so that your computer can talk to your Android device. If you hit a snag, visit the forums and somebody is bound to be able to help you through it.

Now that we're all on the same page, enable USB debugging on your device (see your devices manual if you need help finding it, and remember it was hidden in Android 4.2), and plug it in to your computer. Now skip past the break and let's begin!

1. The adb devices command



The adb devices command is the most important one of the bunch, as it's what is used to make sure your computer and Android device are communicating. That's why we're covering it first.
If you're a pro at the operating system on your computer, you'll want to add the directory with the Android tools to your path. If you're not, no worries. Just start up your terminal or command console and point it at the folder with the tools in it. This will be the file you downloaded earlier if you use Windows, or the platform-tools folder in the fully installed Android SDK.

Windows users have another easy shortcut here, and can simply Shift + right click on the folder itself to open a console in the right spot. Mac and Linux users need to navigate there once the terminal is open, or install an extension for your file manager to do the same right click magic that's in Windows by default.

Once you're sure that you are in the right folder, type "adb devices" (without the quotes) at the command prompt. If you get a serial number, you're good to go! If you don't, make sure you're in the right folder and that you have the device driver installed correctly if you're using Windows. And be sure you have USB debugging turned on!

Now that we have everything set up, let's look at a few more commands.

2. The adb push command



adb push

If you want to move a file onto your Android device programmatically, you want to use the adb push command. You'll need to know a few parameters, namely the full path of the file you're pushing, and the full path to where you want to put it. Let's practice by placing a short video (in my case it's a poorly done cover of the Rick James tune Superfreak) into the Movies folder on your device storage.

I copied the superfreak.mp4 file into the android-tools folder so I didn't need to type out a long path to my desktop. I suggest you do the same. I jumped back to the command line and typed "adb push superfreak.mp4 /sdcard/Movies/" and the file copied itself to my Nexus 4, right in the Movies folder. If I hadn't dropped the file into my tools folder, I would have had to specify the full path to it -- something like C:\Users\Jerry\Desktop\superfreak.mp4. Either way works, but it's always easier to just drop the file into your tools folder and save the typing.

You also have to specify the full path on your device where you want the file to go. Use any of the popular Android file explorer apps from Google Play to find this. Windows users need to remember that on Android, you use forward slashes (one of these -- / ) to switch folders because it's Linux.

3. The adb pull command


adb pull 

If adb push sends files to your Android device, it stands to reason the adb pull command gets them out. That's exactly what it does, and it works the same way as the adb push command did. You need to know both the path of the file you want to pull off, as well as the path you want it placed into. You can leave the destination path blank and it will drop the file into your tools folder to make things easy.

In this example, I did it the hard way so you can see what it looks like. The path of the file on the device is "/sdcard/Movies/superfreak.mp4" and I put it on my Windows 8 desktop at "C:\Users\Jerry\Desktop". Again, the easy way it to just let it drop into your tools folder by not giving a destination, which would have been "adb pull /sdcard/Movies/superfreak.mp4". Remember your forwards slash for the Android side, and you'll have no problems here.

4. The adb reboot command


adb reboot

This is exactly what you think it is -- a way to reboot your device from the command line. Running it is simple, just type "adb reboot" and enter. Before you say "I can just push the button!" you have to understand that these commands can be scripted, and your device can reboot in the middle of a script if you need it to. And it's a good segue to number five.

5. The adb reboot-bootloader and adb reboot recovery commands



Not only can you reboot your device, you can specify that it reboots to the bootloader. This is awfully handy, as sometimes those button combos are touchy, and if you have a lot of devices you can never remember them all. Some devices (the LG Optimus Black comes to mind) don't even a way to boot to the bootloader without this command. And once again, being able to use this command in a script is priceless. Doing it is easy, just type "adb reboot-bootloader" and hit the enter key.

Most devices can also boot to the recovery directly with the "adb reboot recovery" (note there is no hyphen in this one) and some can't. It won't hurt anything to try, and if yours can't nothing will happen.

6. The fastboot devices command


fastboot devices 

When you're working in the bootloader, adb no longer works. You're not yet booted into Android, and the debugging tools aren't active to communicate with. We use the fastboot command in it's place.
Fastboot is probably the most powerful tool available, and many devices don't have it enabled. If you're does, you need to be sure things are communicating.

 That's where the fastboot devices command comes into play. At the prompt, just type in "fastboot devices" and you should see a serial number, just like the adb devices command we looked at earlier.
If things aren't working and you are using Windows, you likely have a driver issue. Hit those forums for the answer.

7. The fastboot oem unlock command



The holy grail of Android commands, fastboot oem unlock does one thing, and one thing only -- unlocks your Nexus device (or an HTC device using their official tool). If you're using a phone from a different manufacturer, you have a different method of unlocking things -- maybe with ODIN or .sbf files -- and this won't apply to you. We're including it because even if you don't need it, it's an important part of Android's openness.

 Google doesn't care what we do with phones or tablets that we've bought, and include this easy way to crack them open. That's something you usually don't see from any tech company, and a big part of the reason why many of us choose Android.

Using it is easy enough. Once you've used fastboot devices to make sure everything is communicating, just type "fastboot oem unlock" at the prompt and hit enter. Look at your device, read carefully, and choose wisely.
Protip: Using "fastboot oem unlock" will erase everything on your device

8. The adb shell command


adb shell 

The adb shell command confuses a lot of folks. There are two ways to use it, one where you send a command to the device to run in its own command line shell, and one where you actually enter the device's command shell from your terminal. In the image above, I'm inside the device shell, listing the flies and folders on the device. Getting there is easy enough, just type "adb shell" and enter. Once inside, you can escalate yourself to root if you need to. I'll warn you, unless you're familiar with an ash or bash shell, you need to be careful here -- especially if you're root. Things can turn south quickly if you're not careful. If you're not familiar, ash and bash are command shells that a lot of folks use on their Linux or Mac computers. It's nothing like DOS. 

The other method of using the adb shell command is in conjunction with one of those Ash commands your Android device can run. You'll often use it for more advanced tasks like changing permissions of files or folders, or running a script. Using it is easy -- "adb shell <command>". An example would be changing permissions on a file like so: "adb shell chmod 666 /data/somefile". As mentioned, be very careful running direct commands using these methods.

9. The adb install command


adb install 

While adb push can copy files to our Android devices, adb install can actually install .apk files. Using it is similar to use the push command, because we need to provide the path to the file we're installing. That means it's always easier to just drop the app you're installing into your tools folder. Once you've got that path, you tell your device to sideload it like this: "adb install TheAppName.apk".
If you're updating an app, you use the -r switch: "adb install -r TheAppName.apk". There is also a -s switch which tries to install on the SD card if your ROM supports it, and the -l switch will forward lock the app (install it to /data/app-private). there are also some very advanced encryption switches, but those are best left for another article.

And finally, you can uninstall apps by their package name with "adb uninstall TheAppName.apk". Uninstall has a switch, too. The -k switch will uninstall the app but leave all the app data and cache in place.

10. The adb logcat command


adb logcat 

The adb logcat command is one of the most useful commands for some folks, but just prints a bunch of gibberish unless you understand what you're seeing. It returns the events written to the various logs in the running Android system, providing invaluable information for app developers and system debuggers. Most of us will only run this one when asked by one of those developers, but it's very important that we know how to use it correctly.

To see the log output on your computer screen, just type "adb logcat" and hit enter. Things can scroll by pretty fast, and chances are you won't find what you're looking for. There are two ways to handle this one -- filters, or text output.

The filter switch is used when a developer has placed a tag in his or her application, and wants to see what the event logs are saying about it. If it's needed, the developer will tell you what tag to append to the command. The text output is more useful, as it logs to a .txt file on your computer for reading later. Evoke is like so: "adb logcat > filename.txt". Let it run while you're doing whatever it takes to crash the app or system program you're debugging, then close it with the CTRL+C keystroke. You'll find the full log file saved in the directory you're working from, likely your tools folder. This is what you'll send to the developer.

Be warned that sensitive information can be contained in the log files. Be sure you trust the person you're sending them to, or open the log file in a text editor and see just what you're sending and edit as necessary.

There are plenty of other switches for the logcat command. Savvy developers can choose between the main, event, or radio logs, save and rotate log files on the device or their computer, and even change the verbosity of the log entries. These methods are a bit more advanced, and anyone interested should read the Android developer documentation.

Bonus: The adb sideload command


adb sideload 

This one's relatively new, and it's one of the easier ways to update a stock Nexus device. Every over-the-air update downloads the update file from a public URL. That means you can download the update and install it manually without having to wait for your phone to have the update pushed to it. We call it "manually updating," and the end result is the same as if you wait. But we hate waiting.
All you have to do is download the update to your computer. Plug your phone into the computer. Reboot into recovery on your phone and choose "Apply update from ADB." Then hop into your favorite terminal/command line and type "adb sideload," with the variable pointing to the update you downloaded. Let things run their course, and you're golden.

And there you have it. There are plenty more commands to learn if you 're the type who likes to learn commands, but these 10 are the ones you really need to know if you if you want to start digging around at the command prompt.

Unlock an Android Device without Internet Access – Using ADB commands

Unlock an Android Device without Internet Access – Using ADB commands

My Android tablet is  locked because too many wrong pattern attempts.  When entering a wrong pattern 20 times (you may be not stupid to enter it wrong 20 times, but your child or someone else who wants to lock your device what happen ? ) your devices is locked and asking to unlock it via your google username and password. You are lucky if the device locked with Wifi on or mobile data network on. Then you can simply log into the google account and unlock it. But I’m not that much lucky and my tablet was in “Airplane mode on” with “Wifi off”.

Android device lock with too many pattern attempts
Android device is locked with too many pattern attempts


Android should have a method to turn on wifi or mobile networks when device is locked. But no, there is no such a method :-/


I did lot of google searches and most of them end up with hard resetting the device. If you hard reset all the data are gone. I tried it too, but because of some problem(it may be the device model), my resetting was stuck in middle of the process. Finally I found a solution to access the device from a PC via a USB cable (ADB Commands). For this method you have to have enabled USB Debugging on the device before it is locked. Luckily I had enabled it before it is locked.  (As I saw, for rooted users USB Debugging is not required — but you might need to manually mount the/data partition. Actually I didn’t try it and don’t know how to do it as my USB debugging is enabled.)
Ok here is the solution for devices which have enabled USB debugging ,

Open the command prompt (cmd) in Windows
Change directory to the android SDK platform tools (cd C:\Program Files\Android\android-sdk\platform-tools)
Type following commands in cmd
  • adb devices (verify device is identified by pc. If not reconnect device and try again. it should display “device” with a serial no)
  • adb shell
  • cd /data/data/
  • sqlite3 settings.db
  • update system set value=0 where name='lock_pattern_autolock';
  • update secure set value=0 where name='lock_pattern_autolock'; (for some devices update “system” is enough but I had to update “secure” too)
  • update system set value=0 where name='lockscreen.lockedoutpermanently';
  • update secure set value=0 where name='lockscreen.lockedoutpermanently';
  • .quit
  • exit
  • adb reboot
Now your device should be unlocked. If not do this step too,
  • adb shell rm /data/system/gesture.key (I didn’t have to do it. But it had mentioned here)

Here what I have done is clear lock patterns and remove the permanent lock from the database. Yes here I have break the security, but saved my device as can be used again. If you are concern about the security of your device “Always keep off USB debugging mode“. But I don’t know what will happen to your important data when someone locked your device.

If you know about a better solution, add it as a comment here. It will help others too.
Update 18-05-2013

Important Comments
ryo :
Ashutosh :
checky :

Saturday, May 18, 2013

How to Run Ubuntu on your Android Tablet

 How to Run Ubuntu on your Android Tablet

What You'll Need:

So, if you haven't figured it out yet, Android is built off of the linux kernel. Therefore there are many ways in which you can get your favorite distributio of linux working. Okay so let’s get started. On in order to do this you will need a rooted tablet. For the whole process we’ll be using adb, so if you already have it setup on your computer good for you. If not, no need to worry I included it in the zip file. Just make sure that you install the drivers. (check the vendors or website, or just google search "tablet name" drivers.)

Step 1:

Download and extract the

Step 2:

Connect your tablet to your computer and transfer "" and "busybox" file from the Ubuntu zip you just extracted. Place those files on the root of your Sdcard. (If you already have busybox installed you can skip this step). Now transfer the rest of the Ubuntu folder to your SDcard.

Qemu Manager
Now, with your tablet still connected to your computer and USB Debuggning on (settings-developers options-USB debugging) go and open Command prompt on your PC. Then you want to change the directory to your unzipped Ubuntu folder. So type in "cd [your directory]" i.e. cd C:/users/david/documents/ubuntu

Step 4:

Now time to install busybox. Once again, if you know you already have busybox installed skip this step. Type in (without quotes) “adb devices” if your device doesn’t come up, that means its not connected, and chances are you need to install the drivers. Now type: (without quotes) "Adb shell" (hit enter) "Su" (enter) "Cd /sdcard/ Sh" (enter) (if it says already exist, then that’s fine)

Qemu Manager

Step 5:

Now time to get ubuntu actually running. Type: "Cd /sdcard/ubuntu" (enter) "Sh" (enter) "Bootubuntu"
Install Windows XP

Congratulations, but wait there's more...

Now we need to update the packages, but they’re out of date, so we need to use this clever work around. (Thanks to Zedomax for this one) Type: "Cat>etc/apt/sources.list" ( hit enter) "deb karmic main universe" (hit enter) Then hit control D twice to bring you back to local host. Finally type in: "apt-get update" (enter) It will update. Lastly is to get into the vncserver itself.

Setting UP VNC

Type "apt-get install tightvncserver" (enter) "export USER=root" (enter) "vncserver –geometry 1280x800" (hit enter)
It will then prompt you to make a password. You can create it, and voila! You’re done. On your tablet go into android vnc (you can download it from the market) nickname can be anything you want. Password is the password you created. Address is localhost. And port is 5901. Then click connect and it’s there. Boom!!!!

Install Windows XP Install Windows XP

How to Run Windows XP on Android

 How to Run Windows XP on Android

Congratulations. So you want to run Windows XP on your Android device. The process is pretty easy and only takes around 30 minutes, but the time may vary depending on your computer speed. To get started, you will need to have a .iso format of Windows XP. If you have your windows' disc, then you could use programs such as ISOBurner to make an ISO form it. After you have that all figured out, continue to download the rest of the items above.

Step 1:

First, let's unzip the SDL Zip. Then transfer the SDL folder root of your SDcard.

Transfer SDL Folder

Step 2: Installing Windows to IMG File

First, on your computer open up Qemu manager. (Start-All Programs- Qemu Mnager). Go to the tab that says VM and click "Create New Virtual Machine" Give it a name, click next. For ram space, generally between 512mb to 1gb is good. This is the ram space it will utlise while you install it on your pc, nothing to do with the ram that will be avilable on your phone. Afterwards click finish.

Now, let's extract the folder you downloaded earlier. Their should be a file inside that's 1.5GB.

Installing IMG File:

Now, in Qemu Manager, you need to specify the blank img file to use for HD0 (Hard Drive Zero). Go to the drives tab, then HD0 and find the "c.img" you just extracted; hit okay. Now go to the CDROm option and search for your WIndows XP.iso file. Once you find it, hit okay. Then go to the little green arrow at the top, and click it (Run Button). Boom it should be running!

Qemu Manager

Installing XP

Now what you want to do is run through the installation (it will take nearly an hour depedning on your computer) until Windows XP is installed. Once the installation finishes you can exit.
Install Windows XP


Great, now that Windows XP is installed on the IMG file you're ready to trasnfer it to your phone. Connect your phone in USB storage mode (or MTP). Next, extract the that you downloaded earlier, and trasnfer it to the root of your SDCard. Afterwards, transfer your C.img file to the root of your SDcard as well.

On your Phone:

Make sure you downloaded Bochs from the Google Play Store. Now launch it, and Windows XP should boot up. Give it a second as it's not the fastest thing to work with. And that's it, you're successfully running windows XP on your phone.

Play PSP Games on Android

 Play PSP Games on Android

What You'll Need:

  • Mid-High End Android Phone/Tablet
  • cube.elf
  • PSP .iso or .cso [Google seacrh ;)]

So playing PSP games on your Android device used to be a topic only found in a science fiction story. However, thanks to the app, PPSSPP, it's possible to play some PSP games on your Android device. Now, like any other novelty, there are many bugs and items that need to be worked out. Needless, to say, their are only a few games compatible at this moment. You can check an up to date list here

Step 1:

First, install PPSSPP, and download the cube.elf file.

Step 2:

Now the hardest part, finding a comtible game. All I can say is Google search is your best friends for these things. Once you found the .cso or .iso version of the game you would like to play, transfer it, along with the cube.elf file to somewhere on your SDcard.
Qemu Manager
Now on your device open up the app. Go to load, and find where you placed the .elf file. Once you find it, select it and if successful a spinning cube should display, this lets you know that your device is compatible.
Qemu Manager


Go back to the main screen, go to load and select your game. If successful, it should open it. BOOM! You just got a psps running on your device. If it doesn't load, then the emulator is probably not able to handle it at this current time, check back later for some more updates

Play PS1 game On Android Device

An Easy To Follow Guide On Playing PS1 Games On Your Android Device. 

I'm Using The Galaxy Note 2 & It Works Really Well. You Should Be Able To Use Any Modern Android Device. The Emulator Software Has 3D Rendering And Hardware Acceleration. You Can Also Use OpenGL.

FPse For Android: Download here
Psx4droid: Download here
ROMS (2 Different Sources): Download here (windows) or Download here (Mac)
BIOS File (Scph1001.bin): Download here( Bin Files )


Download and Install FPSE For Android Or PSx4Droid Onto Your Device. Links Are Above.


a. Connect Your Device To Your Computer
b. Make A File On Your Phone or Memory Card And Name It Emulators
c. Create A Sub Folder Within Emulator And Name It Roms


Download The Bios (scph100.bin) and Copy It Into Your Emulator Folder That You Made In Step 2. Links To The Bios Are Above.


Download A Rom And Save It To Your Desktop. Links To Sources For Roms Are Above.


Create A Folder Which Has The Same Name As Your Rom. This Makes It Easier To Find Later On. Extract The Rom To This Folder (It's usually A Rar file).

Now Cut And Paste This Folder To The Rom Folder On Your Memory Card/Phone. (The One That You Created In Step 2)

Important: It's A .bin or .iso file that you need.


a. Open FPSE On Your Device.
b. Load Bios (Settings - Misc - LoadBios) And Click The Scph1001.bin file
c. Click Load Game And Find Your Game You Want To Play.

Tip: Find The Above in Storage - extSdCard - Emulators.


Enjoy Your Game And Hit The Like Button:)

Extra here : Games Collection

Watch here!!! :

Friday, May 17, 2013

Remove Or Skip Pattern Lock On Android Phone / Tablet

 Forgot the pattern is a very common reason to remove Android's Pattern Lock, a user of xda-developers makes it easier for those people who are facing this kind of problem on their Android Gingerbread, Ice Cream Sandwich and Jelly Bean, without discussing much directly follow the instructions below to remove the Android Pattern Lock from your phone.
ways to easily remove pattern lock password from any android phone without rooting.
How to unlock forgotten androids pattern lock:
There are 2 methods and both works well during its testing. No Rooting required but its better that the device is rooted.

Method 1:  

1. First connect your phone to PC via USB cable and don't forget to enable USB debugging in your Android phone.
2. Type or copy paste below commands in CMD
adb shell
cd /data/data/
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
3. All the above commands must type in the separate line, to make sure press enter after typing each line.

4. Reboot you phone.

 On next reboot, you will see pattern lock so don't worry, you'll be able to draw new pattern lock for your device whatever pattern you like.

Method 2:

1. Same like method 1, connect your phone to PC via USB cable and enable USB debugging in your Android phone.
2. Type or copy paste below commands in CMD
adb shell rm /data/system/gesture.key
3. Reboot.

Thats it.

Disclaimer: These methods may and may not work, it may work on some devices and don't on others, so there is no guaranty it will work. [Source: xda-developers]

Modify Apk With DexTool


Dex2jar have the ability to modify the code of an apk.
  1. It first translate the code from dex to jar.
  2. modify .class files in the jar.
  3. It translate jar back to dex and put into apk
  4. sign the apk, and we done the modification.
for demo, we will modify a apk to let it showing a message when it start.
and you need following components in you PATH. android-sdk,ant,dex2jar,jdk6


got an apk


you need an apk, which you didn't have the source. Just for demo, we build a simple hello-world apk by running the following command
android create project --name test_apk --path test_apk --package a.b --activity Main --target 1
cd test_apk
ant debug
cd bin
now we got test_apk/bin/test_apk-debug.apk. we can check it by running the apk inside an emulator.


work with dex-tools

Now we got the apk, and It's time to modify it.
  • Convert the code to a modifiable format.
we can't modify dex or jar(.class) file directly. dex2jar support to assemble/disassemble .class file from/to jasmin file. so we convert the apk to jar and disassemble it.
# convert classes.dex in test_apk-debug.apk to test_apk-debug_dex2jar.jar -f -o test_apk-debug_dex2jar.jar test_apk-debug.apk# verify jar test_apk-debug_dex2jar.jar# convert to jasmin format -f -o test_apk_jasmin test_apk-debug_dex2jar.jar
  • edit test_apk_jasmin/a/b/Main.j to show a toast
.method public onCreate(Landroid/os/Bundle;)V
aload 0
aload 1
invokespecial android/app/Activity/onCreate(Landroid/os/Bundle;)V
aload 0
ldc_w 2130837504
invokevirtual a/b/Main/setContentView(I)V
; Toast.makeText(this.getApplicationContext(), "hi", Toast.LENGTH_LONG).show();
aload 0
invokevirtual android/app/Activity/getApplicationContext()Landroid/content/Context;
ldc "hi"
ldc_w 1
invokestatic android/widget/Toast/makeText(Landroid/content/Context;Ljava/lang/CharSequence;I)Landroid/widget/Toast;
invokevirtual android/widget/Toast/show()V
.limit locals 2
.limit stack 3
.end method
  • repack apk
# build jar -f  -o test_apk_jasmin.jar  test_apk_jasmin/ # verify jar test_apk_jasmin.jar# convert to dex  -f -o classes.dex test_apk_jasmin.jar# make a copy
cp test_apk-debug.apk test_apk-debug-toast.apk# replace classes.dex in test_apk-debug-toast.apk
zip -r test_apk-debug-toast.apk classes.dex# sign the apk -f -o test_apk-debug-toast-signed.apk test_apk-debug-toast.apk
  • run the apk
# uninstall previously apk
adb uninstall a.b# install
adb install test_apk-debug-toast-signed.apk# start main activity
adb shell am start -n a.b/.Main


all the above command is for *unix, for windows users, please replace the suffix from .sh to .bat.
and for the zip command, just open the test_apk-debug-toast.apk with winRAR,winZIP or 7z, then drag the classes.dex into it.

Thursday, May 16, 2013

How to remove pattern unlock with ADB and Debugging ON [No-ROOT]

How to remove pattern unlock with ADB and Debugging ON [No-ROOT]
Should work on Android 2.1 and above. This solution won't work in recovery.

*Debugging mode must be on
1. Plug in your phone cable
2. Go to ADB
3. Type the following commands:

adb shell rm /data/system/gesture.key

4. Reboot your device.
5. Draw any pattern to unlock the screen.
6. Go to setting menu and change the screen security to slide.

Wednesday, May 15, 2013

ESET SMART SECURITY 4 and 5,6 Keys !!!!! 13/5/2013

ESET Smart Security & ESET Nod32 Antivirus Keys
Username: EAV-86056534
Password: ha64frvc8s
Expire: 01.11.2013
Username: EAV-86056534
Password: ha64frvc8s
Expire: 01.11.2013

Username: EAV-30326836
Password: ccka4dvsuv
Expire: 16.10.2013

Username: EAV-0086876090
Password: mesvns9ptm
Expire: 10.06.2013

Username: EAV-0086876089
Password: s5jvb4bfe7
Expire: 10.06.2013

Username: EAV-0086749235
Password: 53c44ne27a
Expire: 07.06.2013

Username: EAV-0086749238
Password: 2k2492r3b9
Expire: 07.06.2013

Username: EAV-0086749242
Password: 933frupa3f
Expire: 07.06.2013

Username: EAV-0086749245
Password: hf5memdr5x
Expire: 07.06.2013

Username: EAV-0086749249
Password: absr82kbpc
Expire: 07.06.2013

Username: EAV-0086682501
Password: kande4eaaa
Expire: 06.06.2013

Username: EAV-0086682533
Password: k5btxdasf7
Expire: 06.06.2013

Username: EAV-0086682549
Password: ca9m95u99s
Expire: 06.06.2013

Username: EAV-0086682569
Password: xp7sc3mrkx
Expire: 06.06.2013

Username: EAV-0086623624
Password: 7j97tab4hb
Expire: 05.06.2013

Username: EAV-0086623640
Password: d9nmbcxk68
Expire: 05.06.2013

Username: EAV-0086623656
Password: m3ukf3dh9m
Expire: 05.06.2013

Username: EAV-0086623668
Password: vakutaudf6
Expire: 05.06.2013

Username: EAV-0086623696
Password: vb9jujm23p
Expire: 05.06.2013

Username: EAV-0086586471
Password: n36c4eetk7
Expire: 04.06.2013

Username: EAV-0086586490
Password: sdm36p49vn
Expire: 04.06.2013

Username: EAV-0086586496
Password: 72cmferv6a
Expire: 04.06.2013

Username: EAV-0086586504
Password: 3n63hukucr
Expire: 04.06.2013

Username: EAV-0086586513
Password: n8fs9scmas
Expire: 04.06.2013

Username: EAV-0086549610
Password: 352m38jvua
Expire: 03.06.2013

Username: EAV-0086549621
Password: hfksnsba5p
Expire: 03.06.2013

Username: EAV-0086549650
Password: st94sxtpx3
Expire: 03.06.2013

Username: EAV-0086549654
Password: k82rnee4kr
Expire: 03.06.2013

Username: EAV-0086549689
Password: b8hrdt4jkj
Expire: 03.06.2013

Username: EAV-0086500058
Password: f88tfvb5pk
Expire: 02.06.2013

Username: EAV-0086501586
Password: 8jmfxre6cx
Expire: 02.06.2013

Username: EAV-0086501631
Password: v9jmjam4um
Expire: 02.06.2013

Username: EAV-0086501666
Password: ur6f4ajb6c
Expire: 02.06.2013

Username: EAV-0086501683
Password: xsmae29mt4
Expire: 02.06.2013

Tuesday, May 14, 2013

How To Create A Partition On Micro SD Card ( 2nd ) For Move Android Apps To SD Free

Create a 2nd partition on Android phone’s micro SD card is a good method for the internal memory out of memory issue. Currently android phone has lower internal memory for install applications. As a result of that we can’t install all of our favorite apps. Though now we can completely move all the installed apps to the micro SD 2nd partition.

For instance, we can use Link2SD type root app to move apps to SD card’s 2nd partition. If you use that kind of application, when you mount your SD card to a computer, android mount its first partition, so you can use your external memory apps without any issue. This post I’m going to show you how to create a secondary partition on your SD card without loosing its data. I use “MiniTool” windows software for this process.

Android With SD

When I’m testing, I used my older SD card, but its data not wipe or corrupted. However I recommend you to backup all the data on your SD card.
This process no need to connect your SD card to a separate card reader, you can use it using your phone. But you need to enable change USB connection mode as “Mass Storage mode (MSC)” using your phone’s settings.

I’m not responsible dead SD cards. Applying this tutorial at your own risk.

  1. After you created a secondary partition, every time when you connected your phone into a computer, Android will mount first partition and windows not recognize 2nd partition as a removable disk.
  2. Your files, phone’s camera images will be saved on 1st partition. So when you are creating a 2nd partition, give more space to the 1st partition.
  3. In-addition to that, your phone will be displayed your 1st partition size as the SD card size. 2nd partition is completely hidden to the user. As I mentioned earlier, this new partition can only recognize Link2SD type special apps.

How to create a secondary partition on micro SD card.

  • Connect your phone to the computer via USB cable.
  • Run the MiniTool Partition.
  • Mini tool now displays your SD card under “Disk 2″. If it’s not displaying your SD card go to its “General>Relocate Disk Information“/ Then on your phone verify you enable “Mass Storage Mode” .
  • Select your SD card and click “Move/Resize”.

Start creating 2nd partition with minitool
  • Now “Move/Resize window” will open, in its “Partition size” select your first partition size. It will use for saving all your stuff. For instance if you have a 1 GB SD card and you select 200MB, your first partition is 200MB. (First partition will save your media files, camera photos, etc. )

Applying space to 2nd partition
  • Click “OK”
  • Now select “Second partition” by click on it.
  • Click “create” button at the top of the “Mini tool” window.

Create 2nd partition
  • In “Create new partition” windows, under the “label” type a suitable name, “Create as” select “Primary” and change file system as “ext2, ext3, FAT 32, or swap partition” and select desire driver letter. ( Note! Some device can’t detect FAT 32/16 as system file so if its fail to detect second partition again change the file system as ext2or ext 3)

New partition settings
  • Click “OK”
  • Now click “Apply” and “Apply Changes” dialog click “OK”.

Start creating partitions
  • Wait for a few seconds to complete this process.

New partition creating progress
  • If you receive “Apply all the pending changes successfully” you have done.

Confirmation message
  • Click OK.
  • Disconnect your phone from the PC and restart your phone.
You just finished. Now you can change your phone’s “USB connection mode” as “Media transfer mode (MTP)”.

Now you can completely move your phone apps to this new partition using our “How to completely move android apps to SD card second partition with root” post. It’s more effective than the native apps2SD method.

Monday, May 13, 2013

How to move almost all Android apps to SD card (no root required) 2013

How to move almost all Android apps to SD card (no root required) 2013

of the most anticipated additions to Android 2.2 (aka Froyo) was ability to install applications to SD card, because it helps to free internal memory. When internal phone memory gets full, Android users have two problems: 1) users can’t install any more apps and 2) phone starts working slowly. The slow down is caused by the lower speed of disk write operations to the internal memory (see this post for more information on this topic), but the bottom line is that having low available space in the internal memory is not desirable.

So what should a user do when Android phone is running out of internal memory? Uninstalling rarely used apps is an obvious and easiest solution. Moving apps that support Froyo’s apps2sd feature to SD card is another option. However, for this feature to work developers need to enable apps2sd in their apps and unfortunately many large apps still do not support it.

It turns out there is a hack that lets you move almost any Android app to SD card, even if the app developer did not enable this option. And the best part: obtaining root is not required for this to work. More about this hack below, but first let’s take look at the limitations of the Android apps2sd feature.
Apps2sd limitations

Apps2sd functionality is a step in the right direction. However, the way it is implemented creates some restrictions which you should know about:

When an app is moved to SD card, portion of that app still remains in the internal phone memory. On average, you can expect that application’s footprint in the phone memory will be reduced by a factor of 2. Note that for some apps the move will save less than 50%, e.g. Google Earth size in the internal memory reduces from 20.5 MB to 15MB, Adobe Flash Player 10.1 – from 12.4 MB to 8 MB.
If you use an app widget on your home screen, this app should not be moved to SD card, because the widget will stop working.

Android OS doesn’t have any batch tools to move all movable apps to SD card at once. You will need to manually move one app at a time by going through the list of installed apps in Settings->Applications->Manage Applications.

System apps such as Maps and Youtube cannot be moved to SD card using stock firmware on unrooted phone. On some phones Adobe Flash Player is pre-installed as a system app and also cannot be moved. Providers may also install bloatware as system apps, which also cannot be moved on unrooted phone. However, on a rooted phone system apps can be deleted or moved – see FAQ for details.

If you re-flash phone’s firmware, some backup applications may not restore your apps to SD card, but will restore them to the phone memory.

Despite these restrictions, moving apps to SD card is a good way to free up internal phone memory and speed up your Android phone.
Moving (almost) all Android apps to SD card

To run commands which will enable Move to SD card button for most installed apps, you need to have adb executable on your computer. Adb stands for Android Debug Bridge and is used for Android software development, but it is a very useful tool to have for any advanced Android user. You do not need to have a rooted phone to run adb commands.

To download the latest version of Android SDK (which includes adb executable), follow instructions from step 2 in the Installing the SDK article from the official Android development site. Note: you do not need to install any other software such as Eclipse for this procedure.
After downloading the archive of the SDK, unzip it to any folder and remember its location (let’s call this folder <sdk>).

If you are installing Android SDK on Windows machine, you also need to install USB driver as described in USB driver for Windows section.

Connect the phone using USB cable and do not enable USB storage mode. Go to Settings -> Applications -> Development and enable USB debugging.

Start terminal window on your computer (on Windows: click Start, type “cmd” and press Enter).
In the terminal window, navigate to folder containing file named “adb” (<sdk>\platform-tools folder) using this command: cd “full-path-to-sdk-platform-tools” (replace “full-path-to-sdk-platform-tools” with an actual path as shown in the screenshot below).

Type the following lines in the terminal window and press Enter after each line:
adb devices

This checks that the phone is connected and is in the correct mode. You should see one entry in the list of the attached devices. If you get “device not found” error, see Troubleshooting section below.
adb shell

If you get “cannot find file” error and are using Mac or Linux, instead type: ./adb shell
pm set-install-location 2

(If this command doesn’t work try using the “old” command: pm setInstallLocation 2. Thanks to polosco for the tip.)

Command prompt commands on Windows
Now on your phone go to Settings->Applications->Manage Applications.
If you have Android 2.3 or later, click on USB Storage tab (may be called SD card). This tab shows a list of apps that either can be installed to SD card or are already on SD card. The ones that have checkbox on the right side are already moved to SD card (credit to Michael Scully for the tip).
On Android 2.2 and earlier if you don’s see USB Storage or SD Card tab, click on All tab.

Android USB storage tab
Press hardware Menu button and select Sort by Size.
Tap on each app that is taking significant amount of space and tap Move to SD card button. Press hardware Back button and repeat.
(optional) To change the default installation location for new apps back to the internal phone memory, go back to your terminal window and type:
pm setInstallLocation 0
(important) Go to Settings -> Applications -> Development and disable USB debugging. Leaving USB debugging enabled makes your phone vulnerable (e.g. lock pattern can be reset).

Moving Android Adobe Flash player 10.1 to SD card (apps2sd)
Share your experience (optional, but greatly appreciated)

To help fellow Android users know whether this procedure will work on their phone, please submit this form (link: Google Forms) indicating whether it worked for you or not. Once sufficient number of responses is submitted, I will update this post with the results.

“Device not found” error in step 7. Make sure that the phone is connected and is in the USB debugging mode (step 4). On Windows, this error can also mean the driver is not installed properly. Double check that you followed USB driver for Windows steps. If you still are getting this error, try installing a driver for your manufacturer from this link: Tether “ADB” Driver Installation for Windows.

“Permission denied” error: make sure that you correctly typed commands.

Q: Does my phone need to be rooted for this hack to work?

A: No.

Q: Do I need to setup a full development environment (Java, Eclipse) for this to work?

A: No.

Q: Can I move systems apps such as Maps, Youtube, Adobe Flash Player to SD card?

A: On unrooted phone using stock firmware, no.

Q: I don’t have time for this hack. How can I check which of my installed apps officially support moving to SD card?
Install “App 2 SD” application from Android Market and it will list applications for which developers enabled apps2sd support.

Q: Can I move all apps to SD card in one operation?

A: Using stock firmware, no. If you know a way to do so, please let me know in the comments.

Q: Can I delete bloatware apps installed as “system apps” by the carriers?
Yes, but only if you root your device. With a rooted phone you could delete unused system apps, but it gets a bit complicated. Deleting some apps may cause problems with subsequent OS updates, so you should be careful. See this list for Android system apps can be safely removed. Instead of deleting, you can “freeze” unused system apps using Titanium Backup. Freezing an app will remove it from the app drawer and memory and will make sure it is never launched, but it will not free any space in the internal phone storage.

Q: Can I move system apps such as Gmail, Google Maps to SD card on a rooted phone?
A: Thanks to Dominique Tardif for this tip: “You have first to uninstall any updates to the system apps in question. Second, using a rooted file manager, delete the original apk from /system/app (android keeps the system app apart from the updates, the latter being at /data/apps). Once this is done, reboot and reinstall the app from the market. It will be installed as a user app and as such will be movable to the sd card. As an example, my gmail, facebook, maps etc. are all on my sd card now.”
Q: Can I move system apps to SD card if I’m using a custom ROM?

A: Yes. The most popular “aftermarket” Android firmware CyanogenMod puts the absolute minimum of the apps in the system folder. CyanogenMod 7 also by default enables the hack described in this post to allow most apps to be movable to SD card. As a result, many Android apps such as Maps, Youtube, Gmail can be moved to SD card on CyanogenMod 7, while they are unmovable to SD in the stock firmware. Note that to install CyanogenMod the phone doesn’t need to be rooted, but bootloader needs to be unlocked.

( Method 2 )

Simply download and install the android SDK, in cmd prompt, go to the directory of SDK, cd into "platform-tools" directory, and type adb shell.

A $ should appear in new line, then type pm setInstallLocation 2 and press enter. the text pm setInstallLocation 2 should appear in the new line again.

Now close the command prompt, disconnect the phone and restart the phone.
Your apps should now move to SD card by default.

Source: XDA-developers.

Use ADB Method to Install apps or Move installed applications to SD Card on your Android phone

There are many android applications present on Google Play Store that are capable to move or install apps on SD Card. The good example is App2SD which I have used but it is failed for some Android applications like Adobe Flash Player, Screenshot and so on.

There is better alternate solution which is ADB method (ADB stands for Android Debug Bridge). Below are the screenshots BEFORE and AFTER applying this ADB method:

These are the steps of ADB method:

(1) Download and install Java. Skip this step if JDK (Java Development Kit) is already installed on your Windows OS.
(2) Download and install Android SDK . It is very important that the installation path must be “C:\android” to avoid any confusion.

(3) Run Android SDK Manager by going to “Start Menu > Programs > Android SDK Tools > SDK Manager”.

Select the packages like Android SDK Tools, Android SDK Platform-tools and Google USB Driver Package and click “Install Packages” button.

(4) On your Android device (Qmobile Noir A2), go to Menu > Settings > Applications > Development > USB debugging (check: ON). Select Allow USB debugging : OK.

Before proceeding, make sure that you have installed the USB drivers from Qmobile driver CD. Now connect your mobile to PC via USB cable which will automatically start the Qmobile PC Suite application. Just close it (don’t connect it).

For Windows XP users:

(a) Run Command prompt by going to Start Menu > Run

(b) Write cmd and press OK. The command prompt window will open.

(c) Type cd C:\android\platform-tools and press ENTER key.

(d) Run command adb devices and press ENTER.

This will show the list of all devices attached.

(e) Run the following command to check the install location of your Android device:

Command # 1:
adb shell pm getInstallLocation
or adb shell pm get-install-location (for ICS versions)

The output will be 0[auto] by default. Below are the options you have:

0[auto] : Installation to auto location decided by Android OS
1[internal] : Installation to internal storage of mobile
2[external] : Installation to external media like SD Card

To set SD Card as default install location, run this command:

Command # 2:
adb shell pm setInstallLocation 2
or adb shell pm set-install-location 2 (for ICS versions)

To verify that above command worked correctly, you can run Command # 1 again.

To change the install location to 0[auto] again, run this command:

Command # 3:
adb shell pm setInstallLocation 0
or adb shell pm set-install-location 0 (for ICS versions)

Run Command # 1 again to verify the install location:

You can simply unplug your mobile from PC after setting install location to SD Card.

I have made this tutorial simple for inexperienced Android users. If you have any question related to this article, post it here.