Monday, March 24, 2014

Recipe: Tomato Basil Soup

    Preparation time - 35 to 45 minutes


    1. Tomatoes - 5 large (on the vine tomatoes) -Diced
    2. Onions - Half of Big onion - Finely Chopped
    3. Green Pepper - Half - Finely Chopped
    4. Carrot (Optional) - 1 Finely chopped
    5. Basil - 5 to 8 leaves - Finely chopped
    6. Cilantro/Coriander leaves  - For Garnish
    7. Garlic - 1 Clove  - Finely Chopped
    8. Green Chilli - 1 (Optional) - Finely Chopped
    9. Spring onions (white part only) - Chopped
    10. Chilli powder - 1/2 Spoon
    11. Turmeric powder - 1 pinch
    12. Dhaniya Powder - 1 1/2 spoons
    13. Milk  or Sour Cream - 5 spoons
    14. Butter - 1 Spoon
    15. Corn Flour - 2 spoons
    16. Cumin - 2 spoons
    17. Vegetable Oil - 4 spoons
    18. Salt - 1 to 2 spoons
    19. Bread slice - 1


    • Heat a pan. Add 1 spoon of vegetable oil.
    • Add the Cumin seeds. Immediately add the Garlic, Green Chilli. Saute them for 10-20 seconds
    • Add the Finely chopped onions, carrot and Green pepper. Saute for 2  minutes.
    • Add a pinch of salt.
    • Transfer the contents to a blender. Blend for 2 minutes.

    • Heat the pan again.
    • Add 1 spoon of Vegetable Oil.
    • Add the chopped tomatoes and cook for 2 to 4 minutes.
    • Transfer the tomatoes to the blender to add with existing contents.
    • Add the dhaniya powder.
    • Blend for  5 minutes.

    • Heat the pan and add another 2 spoons of oil.
    • Pour the puree in the pan.
    • Add Turmeric powder. Add chilli powder.  Add salt (as per need)
    • Cook for 8 to 10 minutes until the color changes
    • Mix 2 spoons of Corn flour in 1 cup of water. Add in to the boiling soup. Boil for 5 mins
    • Add the finely chopped spring onions and basil.
    • Add the butter. Add the sour cream or milk.
    • Add 1 or 2 cups of water to get desired consistency.
    • Allow Boil for 10 minutes (cover if needed) . Meanwhile prepare bread crumbs.

    • Prepare Bread crumbs -
      • Cut the bread slice into 9 to 16 pieces
      • Heat a skillet to high flame for 5 mins.
      • Lower the flame. Add 1/2 spoon of butter
      • Add the bread pieces and toast to golden brown on low flame.

    • Serve in a bowl.
    • Garnish with Coriander leaves and toasted bread crumbs. 

Tuesday, September 04, 2012

How to install Hyper-V client role on your Windows 8 even though your proceessor does not have SLAT (ofcourse HypervV does NOT work though)

After feeling disappointed that I have an obsolete hardware which cannot run Hyper-V client in Windows 8 due to no SLAT, I still didn't give up. Some forums hinted that this would be possible using DISM. (and found that this is possible to install the role. But it does NOT work. Read on...)

I tried with this command to start with:

Started a command prompt with Admin privileges:

C:\Windows\SysWOW64>Dism /online /enable-feature /featurename:Microsoft-Hyper-V-

Deployment Image Servicing and Management tool
Version: 6.2.9200.16384

Error: 11
You cannot service a running 64-bit operating system with a 32-bit version of DI
SM. Please use the version of DISM that corresponds to your computer's architecture.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Some more digging .. and I realised I have to do some steps and it all works :)
Solution: Run the command in C:\windows\Sysnative which avoids redirection.

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Windows\system32>cd ..
C:\Windows>cd sysnative
C:\Windows\sysnative>Dism /online /enable-feature /featurename:Microsoft-Hyper-V

Deployment Image Servicing and Management tool
Version: 6.2.9200.16384

Image Version: 6.2.9200.16384
Enabling feature(s)
Some info lost here....
The operation completed successfully.

After 2 reboots (first one should be a power off ).

HyperV client does NOT work though.. Any ideas?

Sunday, August 19, 2012

Customising you Mini Xplus - Enable adb daemon to listen on wifi automatically or at boot

Warning: Please note that enabling adb on wifi is a serious security hole and anyone can control your device on they have access to your network

Edit 19/8: This doesnt seem to work at boot :(

As Mini Xplus doesnt come with a connectivty cable and we need adb to play with it, we need to connect to it thru manually enabling adb on the device. I was wondering whether this can be done on boot or automatically when wifi is enable and realised it is very simple.

1. Install a free app from Market -> ADB WIFI (shows up as a Green Bug)
2. Launch it.
3. Go to options.
4. Enable the adb at boot option.
5. Test if the app works as expected

Enjoy J

Friday, August 17, 2012

Minimal console distro available for ARM

A 2.5 Mb rootfs (overall within 6 MB) is available. Check this forum post to know about the small micro core linux with root filesystem.  It might run on the Mini Xplus. Not sure. Need to test it.

Root password:

Also, join if you are interested ...,13798.15.html

Customizing your Mini X plus - Free up space on /system

One of the things I did with my Mni Xplus was to free up space on the /system partition.

I removed lots of unwanted apks and my Mini Xplus boots and feels faster.

1. Connect thru adb

adb connect
* daemon not running. starting it now *
* daemon started successfully *
connected to

2. Mount in RW mode.

adb remount
remount succeeded

3. Launch shell and delete unwanted apks. Use command  rm apkname.apk.

adb shell
root@android:/ # cd /system/app
cd /system/app


root@android:/system/app # df
Filesystem             Size   Used   Free   Blksize
/dev                   153M    44K   153M   4096
/mnt/asec              153M     0K   153M   4096
/mnt/obb               153M     0K   153M   4096
/system                251M   195M    56M   4096
/data                    1G   240M     1G   4096
/cache                 125M     4M   121M   4096
/mnt/private           988K   988K     0K   4096
/mnt/sdcard              1G   681M   790M   4096
/mnt/secure/asec         1G   681M   790M   4096
/mnt/asec/com.eamobile.nfshp_row_wf-1    18M    16M     1M   4096

I have listed the apks on my Mini Xplus

root@android:/system/app # ls -l
ls -l
-rw-r--r-- root     root        28845 2012-08-10 04:29 ApplicationsProvider.apk
-rw-r--r-- root     root       109454 2012-08-10 04:27 BackupRestoreConfirmatio
-rw-r--r-- root     root      2366648 2012-07-09 21:48 Browser.apk
-rw-r--r-- root     root       122226 2012-07-09 21:48 CertInstaller.apk
-rw-r--r-- root     root        15675 2012-07-09 21:48 DefaultContainerService.
-rw-r--r-- root     root       459543 2012-07-09 21:48 DownloadProvider.apk
-rw-r--r-- root     root       153030 2012-07-09 21:48 DownloadProviderUi.apk
-rw-r--r-- root     root        31231 2012-08-10 04:28 DrmProvider.apk
-rw-r--r-- root     root      2058319 2012-08-10 04:29 Gallery2.apk
-rw-r--r-- root     root        73728 2012-07-09 19:54 GoogleBackupTransport.ap
-rw-r--r-- root     root       128327 2012-07-09 19:54 GoogleFeedback.apk
-rw-r--r-- root     root      1391661 2012-07-09 19:54 GoogleLoginService.apk
-rw-r--r-- root     root        79327 2012-07-09 19:54 GooglePartnerSetup.apk
-rw-r--r-- root     root       447445 2012-08-10 04:28 GoogleQuickSearchBox.apk
-rw-r--r-- root     root      1007068 2012-07-09 19:54 GoogleServicesFramework.
-rw-r--r-- root     root        21310 2012-07-09 21:48 KeyChain.apk
-rw-r--r-- root     root      1419198 2012-08-10 03:34 LatinIME.apk
-rw-r--r-- root     root      7904048 2012-07-09 21:48 Launcher2.apk
-rw-r--r-- root     root        12372 2012-07-09 19:54 MarketUpdater.apk
-rw-r--r-- root     root        72121 2012-08-10 04:28 MediaProvider.apk
-rw-r--r-- root     root       660234 2012-08-10 04:28 Music.apk
-rw-r--r-- root     root        97319 2012-08-10 04:28 MusicFX.apk
-rw-r--r-- root     root       271117 2012-07-09 19:54 NetworkLocation.apk
-rw-r--r-- root     root       198222 2012-07-09 21:48 PackageInstaller.apk
-rw-r--r-- root     root         3646 2012-08-10 04:27 Provision.apk
-rw-r--r-- root     root       680858 2012-08-10 04:29 QuickSearchBox.apk
-rw-r--r-- root     root        54142 2012-07-09 21:48 SettingsProvider.apk
-rw-r--r-- root     root         4690 2012-08-10 04:27 SharedStorageBackup.apk
-rw-r--r-- root     root       193449 2012-08-02 23:32 Superuser.apk
-rw-r--r-- root     root      1081140 2012-07-09 21:57 SystemUI.apk
-rw-r--r-- root     root       765014 2012-07-09 21:48 TvdFileManager.apk
-rw-r--r-- root     root      1524729 2012-08-10 04:29 TvdLauncher.apk
-rw-r--r-- root     root      6864442 2012-07-09 21:51 TvdSettings.apk
-rw-r--r-- root     root       165413 2012-07-09 21:48 TvdVideo.apk
-rw-r--r-- root     root      3995946 2012-07-09 19:54 Vending.apk
root@android:/system/app #

 I also removed some modules (8188eu.ko,8189es.ko)  from /system/vendor/modules. Not sure if these are needed but my MiniX is working fine.

Saturday, August 04, 2012

Plan/List of articles/How-tos for Mini Xplus

I'm planning to do (/did) some articles/writeups based on my experience with Mini X plus. Some are:

1. How to root a H24 TV Box a.k.a Mini X Plus
2. How to install clockworkmod recovery on the H24 TV Box a.k.a MiniX Plus :)
3. How to recover your X mini /reflash the firmware
4. Customizing your Mini X plus
 a. Free up space on /system
 b. Enable adb daemon to listen on wifi automatically or at boot
5. How to boot Linaro 12.06 on your Mini X
6. How to install CM9(/CM10??) on your Mini X

Do let me know if you all are looking for something else. I will to try to add.

--Updated 19th August 2012

How to install & use clockworkmod recovery on the H24 TV Box a.k.a Mini X Plus

Warning: Just got a note from Disrupter on forums mentioning that if this CWM recovery is flashed, then we would be unable to use the PhoenixCard method of reflashing firmware. So, suggestion is : Dont try this yet unless you know how to go back.
*Credits: Most of this article is based on Kegg’s post on Rikomagic forums . All credits to him.

As the device is same as MK802, the recovery should work. I tried and initially the keyboard didn’t work. Later I realized that the keyboard should be plugged in USB Host socket. Please see the steps below, based on my experience:

2.    Install busybox installer from Android market

3.    Launch buxybox installer and install busybox

4.    Install script manager from android market

5.    Download the MK802 related recovery files

6.    Extract the files and copy to the root of your SDCARD. They will appear under /sdard. 2 .sh and 1 .img files.

7.    Open Script manager.

8.    Navigate to /sdcard.

9.    Click on Click the SU icon on top and click on run. Once it is completed it will show a message indicating Done.

10. Clock on Click the SU icon on top and click on run. You will see a message Done and your device will reboot. You may have to quickly remove your SD card if it is bootable (else it may continue booting this the card, in my case Linaro 12.06).

11. If all works well, you will see your screen with 4 parts (all similar). But focus on the Top left one.

12. Connect a keyboard (maybe wireless one, so you can be near the TV). Disable the mouse as moving it causes the menu to move. If it doesn’t work make sure you have plugged it in USB host USB socket.

13. Key mappings are as below:

a.    Left arrow <- : Enter

b.    Down arrow V : Down

(not sure about other keys, will check and update if needed)

14. Every time you press down, the screen will go black. Observe that the menu is still moving as you press. So you have to remember which the option active on the screen when the screen is black. Press left key for Enter wherever needed.

15. Insert the SD card. Go to the mount menu, mount the /sdcard. Use down keys and navigate to the main menu.

16. Navigate to backup and restore menu. Choose backup option. The nandroid backup should start.

17. Backup of /system will take considerable time and screen will be black. Keyboard may not respond. Please be patient. Get a cup of coffee J

18. Check after some time and the backup should be done. Choose the reboot option to reboot.

The restore should work but I haven’t tested it yet.

How to enable root prompts on your H24 TV Box a.k.a Mini X Plus

EDIT: Sorry this helps only in enabling the root prompts and not root the device.. Thanks Sacha for helping me realize..

Just got this Allwinner A10 (Cortex A8) based android device and already having some fun.

The device comes with a USB OTG. But unfortunately we do not have a cable for this device as you need a male to male USB cable (checking on this, not sure if it will work). The only way left to connect to the device is wifi. I performed the following steps:

DISCLAIMER: You and only you are responsible for any consequences of doing below steps. I am not responsible if below steps melt your device, explode, disintegrate, etc. This may void your device warranty or make your device unusable. You've been warned!

1.       Enable Wifi. Connect to a Wifi access point
2.       Add a Google account and enable Play Market.
3.       Install Wifi over adb
4.       Install Busybox installer
5.       Install Superuser
6.       Start the app wifi over adb
7.       Click the Turn on Button. This will show you the IP and the port. We need this for the next step.
8.       On your desktop/laptop, Open a cmd prompt: 
adb connect
You will get a message connected to
adb shell
root@android:/ #
9.       The # prompt. This means it is already rooted. However, there is not superuser app installed. And the apps requiring root don’t work as expected yet.
10.   I went ahead and downloaded the Superuser app and installed it. Still the root prompts didn’t not appear. So, the next step was to replace the /system.xbin/su
11.   Download from  which have the relevant files (su). Extract them in  handy location. Simply put them wherever adb.exe is present.
12.   Continuing the adb shell
adb remount
adb shell
#mv /system/xbin/su /system/xbin/su.old
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb reboot
13.    The Device must be rooted now.
14.   Do not turn the automatically alow root access option in superuser app. This caused me problems. Leave it at Prompt

The next articles will be on
2. How to recover your device/reflash the firmware

Monday, August 02, 2010

Adventures of Vmware 2.02 and Firefox > 3.6

I still had some issues with VMWare and Firefox ...

1. VMWare plugin was not working 

Turned out that this was due to the newer versions of Firefox. Simple workaround I read off the web was to just  download and extract an older version of Firefox 3.5 to some folder and run a separate instance of firefox just for the VMWare plugin. I settled for this. This link   will be useful. 

2. Keyboard not working correctly in the VMWare plugin

Once the plugin started working, I got my old problem back. The keyboard was not working correctly inside Windows VMs, where in it would randomly lose focus and gain focus.

I found the solution here.

Simple steps are:
1. Export this variable in the environment right after login such that it will be set before starting Firefox: VMWARE_USE_SHIPPED_GTK=yes
2. Best option is set this variable in the /etc/profile like this:
3. For now just run: 

. ./etc/profile
or Reboot the system
4. Run firefox and check.

For more troubleshooting tips, check Marcus Orfila's page VMware server 2.0.2 on Ubuntu 10.04 

Monday, June 28, 2010

Use a VNC Client to Connect to VMware VMs

Yes. So after hanging around for a while to fix my VM issues, I stumbled on yet another issue.

I was unable to connect to VMs using the VMWare plugin in Firefox. I'm getting a strange error "cannot access Virtual machine console. The request timed out. The attempt to acquire a valid session ticket for "abcdefVM" took longer than expected. If this problem persists, contact your system administrator. ". Before I break my head on this, I wanted to quickly check an easy way to connect to the VMs.

Somewhere, I remember that Vmware uses VNC protocol. So did a quick search and found that we can indeed connect using any VNC client to connect to VMware VMs. Check this VMware KB article.

Technology rocks!

Problems running VMware VM in Linux on a NTFS partition - Solved

I have moved all my VMDK files to a NTFS partition. After this whenever I tried to run a Vmware VM, the mount.ntfs process took up 100% CPU. I upgraded my NTFS Driver as well (with the latest version of NTFS-3G) . 

Finally, after some reading and searching, found a setting to resolve this. All we need to do is to add an entry in the VMX file:
Found the solution here 

Have fun!