Google and Android tips tricks and hacks

Install Kodi on Amazon Firestick

2017-06-11T03:44:00.000-04:00

Jailbreak Amazon Firestick

There are several ways to jailbreak the Amazon Firestick and install Kodi, you can use the Downloader app, or you can install ES File Explorer, connect the firestick via USB to your PC, HDMI to your Television, depending on your device download Kodi from here, then copy and paste the APK to the Firestick through the PC's file manager:

Connect your Firestick via USB to your PC and HDMI to your TV.
On the firestick go to Settings > Device > Developer options and make sure ADB debugging and Apps from unknown Sources is enabled.
Search for ES Explore and Download
Once ES Explorer is ready, open it up and keep it open
Now on your PC in filemanager look for Fire
Now browse to the path where you saved the Downloaded version of Kodi then copy and paste to the Download directory of Fire.
Now use the firestick remote to scroll Downloads in ES Explorer, open the APK and install.

Thats it, enjoy Kodi on your firestick!

Installing Android-x86 4.4 and/or 5.1 on your desktop - PART #2

2016-01-27T02:01:00.000-05:00

Sometime back I posted on how to dual boot android with other operating systems, the instructions mainly were for Ubuntu, these instructions are for those who do not want to play around with the menu.lst or 40_custom. The other day while trying to install Android-x86 and modifying the 40_custom, with bad results I accidently found a workaround and would like to share it.

First off you are still going to need to download something, if one is not available, a partitioning program, Ubuntu Live CD has this option.

Once you have either burned to a CD, or dd Ubuntu to a USB stick, boot your computer, make sure the proper settings in BIOS to boot from CD or USB are enabled, to the run Ubuntu Live.

Now open up your terminal. and in terminal enter:

sudo gparted

From there you are going to create a partition. Right now I am running 4.4, still testing partition schemes and will update, apps seem to keep freezing so am going to see if this has to do something with they type of partition. Just a note, if planning on running Android 5.1, ext4 is the best option, found that in 5.1 apps would not install on ext2 or ext3.

Now that the partition is setup, this is what I did accidently, reboot your PC, remove the Ubuntu Live and insert the Android CD or USB. In Bios, according to the settings of your PC, set to boot from a USB stick. Boot the Android-x86 install, install to the partition, skip the installation of GRUB. When completed, reboot, keep the Android-x86 CD/USB inserted and have a blank USB stick inserted as well. Now install Android-x86 to the USB and say yes to Grub and Grub EFI if asked.

Once that install is done, remove the Android-x86 installation CD/USB, but, keep the one that you installed Android-x86 on inserted in the PC. Now when you start your PC, Android will boot, if you pay attention, you will see a message saying, found android on /dev/sdaX. When done using Android, remove the Android stick and the main OS will boot.

**UPDATE**

After testing on various partions, so far ext4, so far, gives the best proformance when running apps. Have not tried the NTFS or VFAT yet. Because the install does not give the option for ext4, you must manually format the drive/partition to ext4 in gparted.

Unroot and Unbrick LG G Pad V410 AT&T Tablet back to stock

2015-10-20T08:09:00.000-04:00

Again, my curious mind had to fiddle with another Android device causing a hard brick. After seeing here on the AT&T website that Lollipop was out for the LG G pad v410, figured could easily bring the tablet back to stock using this firmware found on XDA. Very bad move, after flashing the firmware using TWRP for the LG-v410, went into settings on the tablet, and did a software update. This caused the tablet to reboot back into TWRP recovery. Next going back to XDA, where I originally downloaded the stock zip file, flashed the stock recovery for the LG-v410. Whoops, now the tablet was, as they call it, hard bricked, now the tablet was stuck on a boot loop showing only the LG Logo.

Anyways, found the LG mobile update tool, the online one did not seem to want to work, so I came across the LG Flash Tool 2014. Only problem was, could only find firmware for newer or older models. Forums and other blogs will say that you can flash the V40010c.kdz, this may work if you did not totally brick your tablet and can still get into recovery, although, if you did what I had done, the drivers are not going to correctly install while in download mode. They may while in TWRP recovery, since you can enable MTP in TWRP recovery.

After much searching, did finally find the KDZ file for the AT&T LG-v410, if you already know what to do, you can grab it right here:

LG G Pad V410(7.0) KDZ AT&T LG Mobile Tool

Make sure your tablet is powered off, if stuck in the LG logo boot loop, hold the volume+ and power button until the tablet powers completely off.
Now while holding just the volume+ button, at the same time plug the tablet into the USB cable to the PC

You should now get this screen:

LG-v410 Download mode

Now grab the LG Flash Tool 2014 along with the correct driver here, this is for offline flashing:

Now that you have everything you need, follow this link and unbrick or simply bring your LG G Pad 7.0 back to factory stock! The directions are for the LG G2, but the same procedure works for the LG G Pad v410.

Making cellphone calls on a 4G LTE android tablet

2015-06-21T04:35:00.001-04:00

Recently, after purchasing a seven inch LG G pad with 4G LTE network capabilities, it never occurred to me that it did not have telephony capabilities. Once the straight talk sim card was in and the correct APN settings were entered, yay 4G boo no cellphone call ability. Anyways, loving a new challenge, it was time to root, unlike the last hack of my MTK6572 Irulu tablet, this was quite different. This tutorial is for the LG G Pad v410, do some research, that is if yours is a different brand, this tutorial may work on other rooted 4g/LTE tablet models.

This tutorial will give you the option of forwarding your mobile number to Google Voice without having to tell everybody to call your Google Voice number. If you haven't done so yet, get a Google Voice number, then under voice settings forward your mobile number to Google Voice.

Enable chat

Manage call forwarding
Follow directions to forward mobile
number to Google Voice number

Step One

XDA developers, my favorite forum for hacks, follow these instructions on installing TWRP and CyanogenMod

Step Two

Method #1 - Open up the dialer and enter *#*#4636#*#*

Method #2 - download this app, Network to open the same settings, this method is a favorite of mine, as we go along, you will see why.

Step Three

Here is the tricky part, first you will need to go into the network, and enable WCDMA. This will allow you to forward your mobile number to Google Voice number.

Enable WCDMA

Next on the rooted tablet open up the phone dialer and make the following changes under settings.

Select settings

Touch calls

Select call forwarding

Change voice mail
numbers to GV#

Step Four

Here are two options VOIP choices:

Method #1 - Download Google hangout and Hangouts Dialer apps from the play store. This is the easiest method, although' if using a Bluetooth for making and receiving calls, not the most efficient.

Method #2 - Enabling VOIP without installing any additional apps. This is done using the dialer, allowing the tablet user to use the device in the same manner as a mobile phone...MY FAVORITE! 😀

After spending countless hours searching for Google Voice's SIP address, finally came across a couple alternative methods, easy to setup, so far great VOIP quality compared to other free PBX sites.

Linking Google voice to SIP accounts enter both accounts.

GVsip offers a free sip account, downside, only 1000 minutes a month, upside, able to make outbound call, as well as, free and easy to use.
Simon Telephonics has a one time fee of $5.99 , upside affordable one time price for unlimited usage. Downside, it's not free and unable to make outbound calls.

Once you have a SIP log in and password, open up dialer and setup your sip setting.

Go into calling accounts

Choose SIP accoumts

Touch accounts

Add username
Password and server
information provided

With Straight Talk, so far, my tablet only allows forwarding, as long as WCDMA or GSM is enabled in network settings. In order for calls to come through when the caller dials my mobile number, LTE ONLY needs to be enabled. Originally when in WCDMA mode, callers got a message that the number did not accept calls. In LTE only it goes straight to voice mail when not forwarded rings to Google Voice when forwarded. After several CyanogenMod updates, WCDMA or GSM now gives the caller a fast busy signal. In order for this trick to work, go back into network settings and enable LTE ONLY.

That's it, enjoy making calls on your tablet just like a mobile device.

06-21-2015 @ 4:53 PM

UPDATE: Realized that when making outbound calla using Simon Telephonics, the call was disconnected when the other party answers. Work around, setup GVSip for out going calls.

Increase/Decrease MTK6572 Cache

2014-10-09T18:11:00.001-04:00

This is going to be somewhat like this previous post, increasing internal storage on the MTK6572, with the exception of increasing, or decreasing, the cache, you can decide which is better.

Somebody asked me about a mod I tried on my tablet where the Cache size was decreased, giving a total of 2.95gb of internal storage. Seeing the internal storage at almost 3gb was pretty cool, although, it seemed as if the performance of the tablet decreased somewhat. After trying the mod again, noticed that some apps slowed down and others would not open. This reminded me of something learned in a college course, the instructor had said something about, the more space you have will give you better speed. Another words, if you install an 80gb hard drive with a RPM of 5400 and 4gb of RAM in your computer. Now if one were to upgrade that hard drive, without changing anything else, to 100gb with a RPM of 7200, you will notice the difference in speed. This made a little light click, thinking, well if there is more cache for apps, would the tablet run faster, in my opinion it does appear to run a little better then before.

What I noticed yesterday is that when playing with the numbers, in order to get a working number to enter in the EBR1, everything has to be in 16 bytes, so that the numbers, for the Internal Application Storage, are divisible by 32. A couple of of the caches sizes I did looked at are 126 MiB and 376 MiB. Not sure if there are any other sizes when it comes to the MTK6572, did successfully make a workable EBR1 work with a cache size of 512 MiB.

--- EBR1
Regular file, size 1 KiB (1024 bytes)
DOS/MBR partition map
Partition 1: 376 MiB (394264576 bytes, 770048 sectors from 1443328)
Type 0x83 (Linux)
Partition 2: 512 MiB (536870912 bytes, 1048576 sectors from 2213376)
Type 0x83 (Linux)
Partition 3: 1.998 TiB (2197353135616 bytes, 4291705343 sectors from 3261952)
Type 0x83 (Linux)

This means, 394264576 bytes / 376 MiB = 770048 decimal value, BC000 hexadecimal value.

BC000 will then be converted to C00B:

00 00 83 00 00 00 00 06 16 00 00 C0 0B 00 00 00
00 00 83 00 00 00 00 C6 21 00 00 00 10 00 00 00
00 00 83 00 00 00 00 C6 31 00 FF 39 CE FF 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA

Where does the extra bytes come from? Well, if you do another math solution, it actually works out a little better when modding. Lets take a number that is divisible by 2, how about 376 MiB, and see what the hex value is.

It's 3F, using some imagination, you have to fill in the blanks zeros, x3xF is read from right to left, entered from left to right as F0 03 now here is a EBR1 from the THL TS MTK6572:

00 00 83 00 00 00 00 56 11 00 00 F0 03 00 00 00
00 00 83 00 00 00 00 46 15 00 00 E0 1C 00 00 00
00 00 83 00 00 00 00 26 32 00 FF D9 CD FF 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA

When you check the EBR1, disktype EBR1

--- EBR1
Regular file, size 512 bytes
DOS/MBR partition map
Partition 1: 126 MiB (132120576 bytes, 258048 sectors from 1136128)
Type 0x83 (Linux)
Partition 2: 924 MiB (968884224 bytes, 1892352 sectors from 1394176)
Type 0x83 (Linux)
Partition 3: 1.998 TiB (2197340552704 bytes, 4291680767 sectors from 3286528)
Type 0x83 (Linux)

Quite slick of them wouldn't you say? This makes it so much easier, if somebody doesn't want to increase the cache by to much or decrease it to small, you just need a number that can be divided by 2. Lets play around with a random number, if the cache is 126, lets just double it, giving a value of 256.

Looking at the hexadecimal value, yes it shows 80, so one has to use their brain power. The hex total needs to be read from right to left, mentally add the 2 missing zeros from right to left then entering the hex value into the EBR1 from left to right. So the Hex value is read x8x0 then entered as 00 08.

This is how it would looked after the change has been made:

00 00 83 00 00 00 00 56 11 00 00 00 08 00 00 00
00 00 83 00 00 00 00 46 15 00 00 E0 1C 00 00 00
00 00 83 00 00 00 00 26 32 00 FF D9 CD FF 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA

This is where all those mysterious bytes come from, disktype EBR1 now shows:

--- EBR1
Regular file, size 512 bytes
DOS/MBR partition map
Partition 1: 256 MiB (268435456 bytes, 524288 sectors from 1136128)
Type 0x83 (Linux)
Partition 2: 924 MiB (968884224 bytes, 1892352 sectors from 1394176)
Type 0x83 (Linux)
Partition 3: 1.998 TiB (2197340552704 bytes, 4291680767 sectors from 3286528)
Type 0x83 (Linux)

Maybe a simple way of explainging would be, to obtain the correct numbers would be, if you are unsure of exactly what was increased/decreased, take the byte value from the original EBR1, subtract the byte value from the new byte value of the modified EBR1:

New EBR1:
Partition 1: 256 MiB (268435456 bytes, 524288 sectors from 1136128)
Type 0x83 (Linux)

Original EBR1:
Partition 1: 376 MiB (394264576 bytes, 770048 sectors from 1443328)
Type 0x83 (Linux)

394264576-268435456=125829120 should be added as USERDATA+FAT+125829120 if decreasing your cache.
394264576-268435456=125829120 should be subtract as USERDATA+FAT-125829120 if increasing your cache

Just like the MTK6572 repartition mod for internal storage, the same rule applies, partition #2 start address needs to be one number higher then partition #1 end address.

gdisk EBR1

Number Start (sector)    End (sector) Size       Code Name
   1         1136128         1660415   256.0 MiB   8300 Linux filesystem
   2         1394176         3286527   924.0 MiB   8300 Linux filesystem
   3         3286528      4294967294   2.0 TiB     8300 Linux filesystem

To fix the second two hex numbers in the EBR1, this means that the end sector of partition #1, 1660415 needs to be 1660416 for the start sector of partition #2. In calculator enter 1660415 as a decimal value and you will get this:

Also, same rule applies, ignore the last two zeros and reading from right to left enter 1956 as 56 19 in your EBR1 like this:

00 00 83 00 00 00 00 56 11 00 00 00 08 00 00 00
00 00 83 00 00 00 00 56 19 00 00 E0 1C 00 00 00
00 00 83 00 00 00 00 26 32 00 FF D9 CD FF 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA

Now check to make sure everything lines up, gdisk EBR1

Number Start (sector)    End (sector) Size       Code Name
   1         1136128         1660415   256.0 MiB   8300 Linux filesystem
   2         1660416         3552767   924.0 MiB   8300 Linux filesystem
   3         3286528      4294967294   2.0 TiB     8300 Linux filesystem

Next make sure to update your scatter file, in terminal again enter disktype EBR1:

Regular file, size 512 bytes
DOS/MBR partition map
Partition 1: 256 MiB (268435456 bytes, 524288 sectors from 1136128)
Type 0x83 (Linux)
Partition 2: 924 MiB (968884224 bytes, 1892352 sectors from 1660416)
Type 0x83 (Linux)
Partition 3: 1.998 TiB (2197340552704 bytes, 4291680767 sectors from 3286528)
Type 0x83 (Linux)

Enter 268435456 into the calculator to get the scatter hex value:

Change:

- partition_index: SYS16
partition_name: CACHE
file_name: cache.img
is_download: true
type: YAFFS_IMG
linear_start_addr: 0x3C140000
physical_start_addr: 0x3BB40000
partition_size: 0x17800000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00

To:

- partition_index: SYS16
partition_name: CACHE
file_name: cache.img
is_download: true
type: YAFFS_IMG
linear_start_addr: 0x3C140000
physical_start_addr: 0x3BB40000
partition_size: 0x10000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00

Unlike the mod to increase the internal application storage, you do not need to worry about partition #3 end sector, this mod will not change it. If you want to move on to the next step, increasing internal application storage for MTK6572, just click the link and follow the directions according to the modified cache scatter text.

**WARNING** THIS MOD IS TRICKIER WHEN CHANGING THE CACHE PARTITION, THESE STEPS ARE IMPORTANT TO SUCCESSFULLY FLASH IN SPFLASH TOOLS

Open spflash tools, select the format tab and you need to manually format the three following areas and enter, ONE BY ONE, the linear_start_addr and partition_size according to the modified scatter.

- partition_index: SYS15
partition_name: ANDROID
file_name: system.img
is_download: true
type: YAFFS_IMG
linear_start_addr: 0x3D40000
physical_start_addr: 0x3740000
partition_size: 0x38400000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00

- partition_index: SYS16
partition_name: CACHE
file_name: cache.img
is_download: true
type: YAFFS_IMG
linear_start_addr: 0x3C140000
physical_start_addr: 0x3BB40000
partition_size: 0x17800000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00

- partition_index: SYS17
partition_name: USRDATA
file_name: data.img
is_download: true
type: YAFFS_IMG
linear_start_addr: 0x53940000
physical_start_addr: 0x53340000
partition_size: 0x3E800000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00

Once that is done, make sure that you do not download the ANDROID USRDATA and CACHE, change them from true to false according to this line:

From

is_download: true

To:

is_download: false

After you have flashed, in clockwork mod recovery, restore ONLY the data and system. Do not do anything with the cache, your backup is according to the old cache size and will cause a soft brick, leaving the device stuck at the boot logo. You will need to create a new backup for future restores according to the cache size.

Update: Tutoial Re-partition the MTK6572

2014-10-06T18:18:00.001-04:00

This is an update from my previous post, the first post works, this mod is a little simpler and when flashing the new EBR1 on the MTK6572, you will not have to do a system restore, it works almost perfectly.

Three things needed that will make this process quick and painless are:

A hex calculator, in Ubuntu, one is actually already installed, this tutorial will also teach you how to use it if you do not already know how, can also use an online hex calculator, here is a link to one. Google is also a good tool for doing mathematical functions using hexadecimal formulas, click here for an example.
A hex editing program, I prefer okteta in Ubuntu, it highlights the hex numbers, making it easier to view.
Linux can use terminal shell, not sure about windows, tried cygwin myself, just did not seem to like the EBR1 files for the MTK6572.

First thing that needs to be done is, in your MTK6572_Android_scatter.txt, you need to add the partition_size of USRDATA and FAT:

- partition_index: SYS17

partition_name: USRDATA

file_name: userdata.img

is_download: true

type: NONE

linear_start_addr: 0x43F40000

physical_start_addr: 0x43940000

partition_size: 0x20000000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: UPDATE

reserve: 0x00

- partition_index: SYS18

partition_name: FAT

file_name: NONE

is_download: false

type: NONE

linear_start_addr: 0x63F40000

physical_start_addr: 0x63940000

partition_size: 0x87040000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: INVISIBLE

reserve: 0x00

Open up the calculator, and under mode, select programming, now make sure that you have Hexadecimal enabled in the calculator and enter the two values, as so, and press enter:

While you have that hexadecimal value available, lets update the scatter text partition_size with the total number, in the USRDATA section, enter the total hexadecimal value, than for FAT 0x0. Found that leaving FAT as 0x0, even with the 110kb leftover internal storage forces that internal storage to become an unallocated space, this makes it easier to hide.

Now change the dropdown from hexadecimal to decimal, and divide that decimal into 32 from, then press enter:

Again, change the decimal drop down box back to hexadecimal, and this is going to be the new hex value in in Partition #2 of your EBR1. Note, in the calculator, the value is actually read from right to left but entered in the EBR1 from left to right, ignoring the 0000 at the end, as I highlighted in the calculator, the number 5382 will be entered as 82 53.

Here is an example of my EBR1 file for the Irulu 7inch MTK6572, I've highligted the first two numbers that are going to be changed:

00 00 83 00 00 00 00 06 16 00 00 C0 0B 00 00 00

00 00 83 00 00 00 00 C6 21 00 00 00 10 00 00 00

00 00 83 00 00 00 00 C6 31 00 FF 39 CE FF 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA

The 00 10 is now going to become 82 53. It is usually a good idea to save your EBR1 under a new name, it will load in SPFLASH tools under any name that you call the EBR1, in this case, it has been named as 2.5gb-EBR1.

In terminal shell, lets check the value of 2.5gb-EBR1, or whatever you chose to name yours:

--- 2.6gb-EBR1

Regular file, size 1 KiB (1024 bytes)

DOS/MBR partition map

Partition 1: 376 MiB (394264576 bytes, 770048 sectors from 1443328)

Type 0x83 (Linux)

Partition 2: 2.610 GiB (2802057216 bytes, 5472768 sectors from 2213376)

Type 0x83 (Linux)

Partition 3: 1.998 TiB (2197353135616 bytes, 4291705343 sectors from 3261952)

Type 0x83 (Linux)

As you can see, the number is exactly the value of my USRDATA+FAT, but....there is one little issue in using the entire value, all MTK6572 that this method has been tested on various devices The full value will not load, I have tried all different methods, just cannot figure out how to get it to work, this may be because the mod does not actually change your blocksmap. In terminal shell, if you type adb pull /etc/dumchar_info, before and after the mod, this is where MTKdroid tools pulls the blocks maps from, it will not be changed. There has to be a leftover value, the smallest being 110kb, in the EBR1, in order for the mod to actually work.

In the area where the old value was 00 10 but now is 82 53, for the first number, every one adds 110kb and for the second set of numbers, every one added is 32mb. The 82 need to be reduced by one, leaving a value of 81, enabling the modified EBR1 to successfully load without issues. If you want to try the full value yourself, don't be surprised when the tablet doesn't get past the boot logo.

Now in terminal, once you have reduced your first number by one, again type disktype 2.6gb-EBR1 and the value is now:

--- 2.6gb-EBR1

Regular file, size 1 KiB (1024 bytes)

DOS/MBR partition map

Partition 1: 376 MiB (394264576 bytes, 770048 sectors from 1443328)

Type 0x83 (Linux)

Partition 2: 2.609 GiB (2801926144 bytes, 5472512 sectors from 2213376)

Type 0x83 (Linux)

Partition 3: 1.998 TiB (2197353135616 bytes, 4291705343 sectors from 3261952)

Type 0x83 (Linux)

If you want, you can subtract that number from the first number, no matter what the size of your total USRDATA+FAT, it will come out to be 131072, which shows on the devices as 110kb.

The next thing is to fix the beginning and end sectors of the EBR1, in terminal enter gdisk 2.6gb-EBR1 and press p.

Number Start (sector) End (sector) Size Code Name

1 1443328 2213375 376.0 MiB 8300 Linux filesystem

2 2213376 7685887 2.6 GiB 8300 Linux filesystem

3 3261952 4294967294 2.0 TiB 8300 Linux filesystem

The end sector, 7685887 needs to be increased by one, there are two ways this can be done, I found the easiest being, taking the number, 7685887, adding one and in calculator getting the hex value, as so:

Just like before, the value 754700 is going to be read from right to left starting with 47 and ending with 75 making C631 become 47 75.

00 00 83 00 00 00 00 06 16 00 00 C0 0B 00 00

00 00 00 83 00 00 00 00 C6 21 00 00 81 53 00 00

00 00 00 83 00 00 00 00 C6 31 00 FF 39 CE FF 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA

Back in terminal shell, when typing gdisk 2.6gb-EBR1, you can see that the end sector of partition #2 is one number less then the beginning sector of partition #3. If you pay close attention though, you will notice that the end sector of partition #3 has reduced, this needs to be corrected in order for a successful flash in SPFLASH tools.

After taking a look at three different MTK6572 EBR1 files, it was discovered that all three ended with a value of 4294967294, to check for yourself, type gdisk EBR1 and you will see that indeed the value is 4294967294. To double check, gdisk your original EBR1 and check the end sector of partition #3.

What I found that works is, and if you want to try this on your own, subtracting the number, 4294967294, which is the end sector of partition #3, from the start sector of partition #3, in the original EBR1, making sure that the decimal dropdown is selected, then switch to hexadecimal, just as so:

Number Start (sector) End (sector) Size Code Name

1 1443328 2213375 376.0 MiB 8300 Linux filesystem

2 2213376 3261951 512.0 MiB 8300 Linux filesystem

3 3261952 4294967294 2.0 TiB 8300 Linux filesystem

Now in your original EBR1 file, you can see that is where the hex value for the number, 4294967294 comes from:

00 00 83 00 00 00 00 06 16 00 00 C0 0B 00 00

00 00 00 83 00 00 00 00 C6 21 00 00 81 53 00 00

00 00 00 83 00 00 00 00 47 75 00 FF 39 CE FF 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA

All that has to be done is to take the same value, 4294967294, subtract that that from new start sector of partiion #3 in the 2.6gb-EBR1:

39 CE will now become B8 8A, in terminal shell, gdisk 2.6gb-EBR1 will now show:

Number Start (sector) End (sector) Size Code Name

1 1443328 2213375 376.0 MiB 8300 Linux filesystem

2 2213376 7685887 2.6 GiB 8300 Linux filesystem

3 7685888 4294967294 2.0 TiB 8300 Linux filesystem

This is going to leave a storage of 110kb for internal storage, When I tried formatting in gparted to hide, gparted said could not do anything with a size of -1mb. After a reboot it disappeared, doesn't even show in my file manager when enabling USB storage. Some system apps are gong to want to use that 110kb for various things. Google Chrome is one example, when trying to share photos in Chrome browser, if that 110kb internal storage is enabled, it will try to use it as a cache, causing a low memory error.

Tutorial: How to repartition and increase app space MTK6582

2014-09-30T12:02:00.000-04:00

Yet another MediaTek Android Tablet/Phone Hack

In order to repartition the MTK6582, all you need to do is refer back to the instructions written here, how to repartition MTK6572. The concept is identical, the only difference is that the MTK6582 has an EBR2, like a few other well known MTK devices. There are tutorials that you may have followed in a few forums, such as this one on XDA-Developers and a few others. The thing I noticed right away is that t MTK6582 is nothing more than an update of the MTK6572.

In terminal shell when you look at the EBR files, you will see something like, when entering in shell:

disktype EBR1

--- EBR1
Regular file, size 512 bytes
DOS/MBR partition map
Partition 1: 900 MiB (943718400 bytes, 1843200 sectors from 165888)
Type 0x83 (Linux)
Partition 2: 126 MiB (132120576 bytes, 258048 sectors from 2009088)
Type 0x83 (Linux)
Partition 3: 2.035 GiB (2185232384 bytes, 4268032 sectors from 2267136)
Type 0x83 (Linux)
Partition 4: 2.000 TiB (2199023255040 bytes, 4294967295 sectors from 144384)
Type 0x05 (Extended)

disktype EBR2

--- EBR2
Regular file, size 512 bytes
DOS/MBR partition map
Partition 1: 1.997 TiB (2195677249024 bytes, 4288432127 sectors from 6390784)
Type 0x83 (Linux)

EBR2 is an extension of your internal storage's partition, so if you want to use all of your internal storage for app storage, all you need to do is change, in the scatter.txt, the section "is_download: for EBR2 from true to false, just like this:

- partition_index: SYS14
partition_name: EBR2
file_name: EBR2
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x5300000
physical_start_addr: 0x4700000
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00

NOTE: If you do not want to use the entire storage, am not sure what would happen if you used the same mod with the EBR2 removed.

To update the scatter.txt codes, just follow these same directions for the MTK6572 so that your partition sizes match the partitions for the USERDATA and FAT.

Tutorial #2: Increase MTK6572 Data/Application Storage- Editing MTK6572 Scatter.txt

2014-09-21T16:58:00.000-04:00

Part Two - Editing Scatter File and Increasing Phone/Tablet Speed

In the first tutorial you learned how to partition your EBR1 to increase your application data storage, in this section I will explain how to edit your MTK6572_Scatter.txt. If the EBR1 is repartitioned and loaded to the phone/tablet, the mod will work, with a few bugs. First off, certain application notifications will not work properly, secondly, the speed of the phone/tablet will decrease considerably. After editing the scatter file, you will notice, even before the repartition, a significant increase in the performance and speed of the phone/tablet.

NOTE: After taking a look at different partition schemes on different MTK6572 phone/tablet, found that the partitioning is not exact, after partitioning you have values hanging around, as stated in the last tutorial, you can either leave a decent amount of internal storage or format the remaining amount as ext4 so that the phone/tablet does not show it in a file manager or settings.

Here is a section of my own scatter file, notice the highlighted parts, these two numbers are what we need to modify.

partition_index: SYS17

partition_name: USRDATA

file_name: nvram.bin

is_download: true

type: NONE

linear_start_addr: 0x43F40000

physical_start_addr: 0x43940000

partition_size:0x20000000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: UPDATE

reserve: 0x00

partition_index: SYS18

partition_name: FAT

file_name: NONE

is_download: false

type: NONE

linear_start_addr: 0x63F40000

physical_start_addr: 0x63940000

partition_size: 0x87040000

region: EMMC_USER

storage: HW_STORAGE_EMMC

boundary_check: true

is_reserved: false

operation_type: INVISIBLE

reserve: 0x00

To get the decimal value for the usrdata/application partition, 0x20000000, it has to be converted to the decimal value, here is a website that will do the conversion if you do not have the appropriate calculator handy:

The decimal value is 536870912.

There are two ways to check and see if the value is correct, the first way is by checking in a terminal shell under Linux.

sudo disktype EBR1

--- EBR1
Regular file, size 1 KiB (1024 bytes)
DOS/MBR partition map
Partition 1: 376 MiB (394264576 bytes, 770048 sectors from 1443328)
Type 0x83 (Linux)
Partition 2: 512 MiB (536870912 bytes, 1048576 sectors from 2213376)
Type 0x83 (Linux)
Partition 3: 1.998 TiB (2197353135616 bytes, 4291705343 sectors from 3261952)
Type 0x83 (Linux)

The value of Partition 2, 536870912 is the size of USRDATA, now lets do the same thing with the partition size for the FAT, 0x87040000, here is the link for the online hexadecimal to decimal calculator again, the decimal value is 2265186304. The second way to check both the two values for USRDATA and FAT partitions can also be done is SPFLASH Tools.

USRDATA & FAT PARTITIONS

Now lets add those two values together, you can do it in a Google search engine, here is one provided for you:

536870912+2265186304

Google Search

The two partitions added together lets you see that the total of your FAT and USRDATA is 2802057216, but, before taking that value and converting it to a hexadecimal value, we need to subtract that little floating value that was left over from the partitioning. Lets go back into the terminal shell and take a look now at the new EBR1 file that was created in PART ONE:

sudo disktype 2.5gb-EBR1

--- 2.5gb-EBR1
Regular file, size 1 KiB (1024 bytes)
DOS/MBR partition map
Partition 1: 376 MiB (394264576 bytes, 770048 sectors from 1443328)
Type 0x83 (Linux)
Partition 2: 2.594 GiB (2785017856 bytes, 5439488 sectors from 2213376)
Type 0x83 (Linux)
Partition 3: 1.993 TiB (2191011479040 bytes, 4279319295 sectors from 7652864)
Type 0x83 (Linux)

The newly repartitioned EBR1 file's partition 2 is 2785017856, this now has to be converted to a hexadecimal value, than changed in the scatter.txt. Here is the same website with the decimal to hexadecimal conversion option, the partition size's hexadecimal value, 0x87040000, is now going to be replaced with 0x10999999.

Now for the FAT we need to find the floating value so that the partition size can be decreased. Although the phone/tablet is showing a one size as pictured, the actual size can correctly be shown by turning on USB storage and looking at it on the PC file manager. Since android does not read partitions the same as Linux or windows, we need to find the actual sizes to be able to configure the scatter text correctly.

In this case, my tablet's real value is 17mb, I needed to find the hex value of that number and change it in the FAT partition of the scatter text. There is no way of finding that actual value when looking in MTK Droid Tools, SPFLASH tools or using the disktype command in a terminal shell. What actually has to be done is you have to take the new partition size and subtract it from the old partition size.

So now we know that, taking the USRDATA and FAT partitions and adding them together gave us 2802057216, now we need to subtract the new partition size from that, which you saw when typing sudo disktype 2.5gb-EBR1. Now in the below search engine you can subtract those two values:

2802057216-2785017856

Google Search

The new value now is 1703936 (17.03936mb), which has to now be converted to a hex value and replaced with the old FAT partition value. Here is the link again for that nifty online decimal to hexadecimal calculator and there is the new value for the FAT partition, 0x10400000. Just a note, I had added one 0 to the end since the scatter file shows eight digits after the 0x for all hexadecimal values.

When you load edited scatter file, make sure to backup the original, SPFlash tools may import all the partitions, there is no need to worry, just make sure to load the appropriate sections when flashing. If you downloaded a nandroid backup, I found it easier to flash everything except for my system, usrdata and cache. Those were reflashed in recovery using the custom clockwork mod that was created in MTK Droid Tools.

After repartitioning and reflashing, MTK Droid tools still reads the old partition schemes. Not really sure where it finds the values yet, working on finding that, possibly hardcoded somewhere in the tablets file system, and fixing it to read correctly, if possible.

The company where I purchased the tablet from had the actual kernel hidden on their download section with another EBR1 that worked when flashed. It increased my usrdata from 512mb to 1.27mb. What was really odd though is that when trying to repartition that EBR1, which nearly used every bit of the FAT partition up, except for about 3-4mb. The repartitioned 1.27gb EBR1 to 2.6gb would not load, just left the tablet frozen in the boot logo. So far have looked at three different MTK6572 partition schemes and cannot figure out how they makeup the values, there has to be some easy EBR tweaker that is used. Unless a bunch of underpaid, overworked nine year old laborors are actually sitting there manually repartitioning Android Tablet MBR/EBR.

How to unbrick and unlock the ZTE Mert straighttalk/tracfone z990g to AT&T z990

2014-09-13T22:14:00.002-04:00

* WARNING I WILL NOT BE RESPONSIBLE IF YOU BRICK YOU PHONE PERMANENTLY - PROCEED AT YOUR OWN RISK *

How to get FTM mode on the ZTE Straighttalk/Tracfone wireless android phone.

StraightTalk/Tracfone FTM mode

Unlocking the ZTE Z990g to ZTE z990 is very easy, to make it even easier, have compiled and provided the files needed to unlock your phone for AT&T, click here to download the files. Unzip and place the image folder on your sdcard just the way it is:

image
- image.bin

After bricking my own phone, this was because I had flashed the wrong recovery before erasing the boot. This caused the phone to get stuck in the boot logo and was only able to pickup DFU mode. Straight Talk probably didn't want to lose customers by making it easy to unlock the bootloader and had ZTE lock it up. Now there is no support anywhere on the net for this phone, unless you are still a Straight Talk customer paying for the protection plan. That probably doesn't cover self maintenance much, just a trade in for something of equal value. Finding this hack is very helpful, in so many ways, once you unlock to AT&T, there is now a working bootloader, download mode and FTM mode.

After performing the ZTE update on-line tool, the phone sometimes goes into download mode. Pressing the power button will not always wake it back up. All that needs to be done is, take off the back cover, there is a reset switch to the right of the camera. Take a toothpick or something that will not damage your phone and press it inside the hole, it should boot right up. If this does not work, take the battery out replace it and hold the reset switch while plugging the phone into the PC then release.

First download Step One RAR file extract the image folder to your sdcard wit the image.bin inside the image folder, on the root of the SDCARD. Power down the phone then press home then volume-up then power, do not press at the same time but in that order. You will see the t flash update, if it takes awhile, that means it is working, if the update completes to soon, this means it did not work. A successful update will go from 1% to 100% twice.

Once that has successfully finished, your phone will power up, give it a few minutes to register. If you want to make sure it really worked, power down, then press volume down then power. The FTM screen should appear like the picture above.

Next download the Step Two RAR file and do the same, extract the image folder, just the way it is, the image folder with the image.bin, on the root of the sdcard.
Last setp, to complete the task, download this T-Flash update this will convert the ZTE Merit Z990G to a full functional ZTE Avail Z990.
Now to update to the latest firmware, is also needed if you want to completely Sim unlock the Merit/Avail, download the ZTE online update tool here and follow the instructions to update your firmware to version P736TV1.0.0B32.

Not sure if after performing the above method actually unlocks your ZTE Z990g to work with an AT&T sim card, did not try a card before performing the below method myself. You can always insert an AT&T sim card to see if it works, if you prefer using AT&T, the below method is really not necessary. The above method will convert your phone from Z990G to Z990, this I do know.

Sim unlocking the Merit/Avail to any carrier

First download QPST Tools, here is version 2.7.411, power down the phone, press volume down then power or volume down and connect to USB port, hold until you see FTM. Now open the software download tool, select the backup tab and backup your NVRAM. Once that is done you can download the unlock tool. Just finished successfully unlocking my converted Z990 from Z990g to work with any network. Here is this Unlock Tool, extract it and run the unlock tool while in FTM mode, enjoy your new unlocked ZTE Merit Z990G. You will need to now go back into QPST Tools Software Download, click on the restore tab and restore your NVRAM, this is because the unlock tool will delete some info and the WIFI will not connect.

Tutorial: How to increase partition on MediaTek Tablets MTK6572, MTK6577 and others

2014-09-01T21:41:00.000-04:00

Phone Storage

2.5gb App Storage

Modding these tablets, turns out, is much easier then modding the models that have a MBR, EBR1 and EBR2. The models with just one EBR1 instead of two and three is actually very simple, for a simple cheap tablet. Now there is a way to take that $60 tablet and turn it into a $250 tablet.

This particular mod is so easy, it took me more than a month to figure it out. After trying all different Apps offered through Google Play Store and others located on XDA developers, nothing seemed to really work, especially for the MTK6572. After reading several articles about modding other MTK tablets, the last being about partitioning, something clicked.

Originally what had gotten the ball rolling was an MBR and EBR1 fie that I had come across on my manufactures website. Their MBR was identical with my tablets MBR, the EBR1 were different. Next, upon flashing the new MBR and EBR1 via SPFlash Tools, it had expanded my internal app storage storage from 512mb to 1.27gb, causing a decrease of my tablet storage from 2.11gb to 1.34gb. According to this read on XDA , the new discovered MBR/EBR1 was not technically possible, it should not have worked, but it did. From that tutorial, you need to edit your MBR along with your EBR1, in this tutorial, there is no need to play with the MBR, you just need to concentrate on the EBR1.

Next, tried all different math solutions, comparing the original EBR1 with the new EBR1. After reading about using partitioning tools, decided to see what would happen if I were to run some command line based partition tools in linux. That is when I discovered just how the partitions on the MTK6572 tablet works.

****WARNING I WILL NOT BE RESPONSIBLE IF YOU PERMANENTLY BRICK YOUR TABLET/PHONE***

After not having much luck using windows or Cygwin, it became apparent that using, what I could, in linux for a linux based tablet would probably go a long way.

Ubuntu Linux programs you will need are:

You can root your tablet either using Framaroot or,

MTKdroid tools from here and, it may or may not allow you to root, if not, then get Framaroot and try, read the tutorial on how to backup your tablet before beginning this mod, MTKdroid tools is what you will need to pull your MBR and EBR1, yes you will need windows, sucks.

Optional, also, very helpful, a good nandroid backup from the play store, a favorite of mine is nandroid backup this will not pull your EBR1 but is a lifesaver in case of a brick.

SPFlash Tools read that tutorial as well.

A Hex editor, some are, wxhexeditor, bless hex editor, jeex or Okteta, I'm using Okteta because it highlights the partitioned numbers making it easy to view.

Google search is a great tool for doing your math solutions, just punch in your numbers in the search bar.

A partition program to examine your mathematical solutions after you changed your EBR1, gdisk works fine, running the command disktype EBR1 and disktype MBR will give you a good understanding of what type of partitions you are working with. Note, DO NOT bother trying to repartition your EBR1 using a partition tool, it will not work. The partitioning program is going to want to modify your partitions to a recognizable partition, nand partitions are not the same and are not listed in these programs.

Lets inspect our MBR and EBR1, it's good to get familiar at what is being worked on. Now that you have pulled the MBR and EBR1 using MTKDroid Tools, open up a terminal shell, navigate to where the MBR and EBR1 files are and enter:

disktype MBR

The output will be something like, here is mine:

--- MBR
Regular file, size 512 bytes
DOS/MBR partition map
Partition 1: 2.000 TiB (2199023255040 bytes, 4294967295 sectors from 1024)
Type 0x05 (Extended)
Partition 2: 10 MiB (10485760 bytes, 20480 sectors from 18432)
Type 0x83 (Linux)
Partition 3: 10 MiB (10485760 bytes, 20480 sectors from 38912)
Type 0x83 (Linux)
Partition 4: 650 MiB (681574400 bytes, 1331200 sectors from 113152)
Type 0x83 (Linux)

Now lets take a look at your EBR1:

disktype EBR1

--- EBR1
Regular file, size 1 KiB (1024 bytes)
DOS/MBR partition map
Partition 1: 376 MiB (394264576 bytes, 770048 sectors from 1443328)
Type 0x83 (Linux)
Partition 2: 512 MiB (536870912 bytes, 1048576 sectors from 2213376)
Type 0x83 (Linux)
Partition 3: 1.998 TiB (2197353135616 bytes, 4291705343 sectors from 3261952)
Type 0x83 (Linux)

This gives you an idea of how far you can expand your storage, looking at the 2TIB makes you wonder, why would they create an MBR/EBR with a 2TIB capability but my internal storage is 4gb total and the tablet only supports up to 32gb? Well, I'm thinking that this is a versatile used partition scheme used on many different devices, it could also be a potential to increase your internal app storage way beyond 4gb + 32gb with other mods down the road. What we want to focus on at the moment is, how much can partition #2 be increased to install more apps.

Now lets get a look at what the partitions look like, again in terminal type:

gdisk MBR

Press p to print the MBR information

The output will look something like this:

Disk MBR: 1024 sectors, 512.0 KiB
Logical sector size: 512 bytes
Disk identifier (GUID): 8092B769-A758-413F-AB79-CCDB0BC73A2F
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 990
Partitions will be aligned on 512-sector boundaries
Total free space is 957 sectors (478.5 KiB)

Number Start (sector)    End (sector) Size       Code Name
   2           18432           38911   10.0 MiB    8300 Linux filesystem
   3           38912           59391   10.0 MiB    8300 Linux filesystem
   4          113152         1444351   650.0 MiB   8300 Linux filesystem

Now enter q to exit

Now lets do the same with the EBR1

gdisk EBR1

Hit p again:

Command (? for help): p
Disk EBR1: 2 sectors, 1024 bytes
Logical sector size: 512 bytes
Disk identifier (GUID): C631D7B1-0586-4F22-A806-1B155BE2BBE7
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 18446744073709551584
Partitions will be aligned on 512-sector boundaries
Total free space is 18446744069416027584 sectors (8.0 ZiB)

Number Start (sector)    End (sector) Size       Code Name
   1         1443328         2213375   376.0 MiB   8300 Linux filesystem
   2         2213376         3261951   512.0 MiB   8300 Linux filesystem
   3         3261952      4294967294   2.0 TiB     8300 Linux filesystem

Now press q to exit

What we want to concentrate on is resizing the second partition. For this mod to work, if you look closely, partition three starts one digit higher from where partition two ends. These are the two numbers that we need to increase but make sure that the end of partition two is one digit lower then the beginning of partition three, else, big ole fat BRICK!

Now open the EBR1 using a hex editing program, here is what you need to concentrate on:

0000:01C0 | 00 00 83 00 00 00 00 06 16 00 00 C0 0B 00 00 00 | ...........À....
0000:01D0 | 00 00 83 00 00 00 00 C6 21 00 00 00 10 00 00 00 | .......Æ!.......
0000:01E0 | 00 00 83 00 00 00 00 C6 31 00 FF 39 CE FF 00 00 | .......Æ1.ÿ9Îÿ..
0000:01F0 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA | ..............Uª

These are the three values that are going to be increased:

00 10 will be 0x0010
C6 31 will be 0xC631
39 CE will be 0x39CE

For every 512mb we are going to add 10 to all three of those values separately, so if you want to increase your partition to 1.5gb, you will need to add 30 to each section. Lets do this in a Google search, enter your number 0x####+30, you can use the one provided below, mine would be 0x0010+30, yours may be different.

Here my value is 0x2E which the same as 0x002E, so now in the hex editor my 00 10 will become 00 2E, the 00 is going to be the same and the 10 is going to become 2E

The next set of number, C6 31 is going to become 0xC631, again in the search enter 0x####+30 (0xC631+30)

My new value has gone from C6 31 to C6 4F, the C6 has actually stayed the same just like before.

Now for the last two numbers, we are going to do the exact same thing, enter your formula below, ie. 39 CE will be entered as 0x39CE+30
Mine has now went from 39 CE to 39 EC.

Now save your editing under a different name, always keep your original, you can name it what ever you want, I will explain how you can select your new EBR1 without having to make any changes to your scatter.txt in SPFlash Tools, lets save it as 1.5gb-EBR1.

Now we are going to check the values in gdisk, open up terminal shell again and type:

gdisk 1.5gb-EBR1

Disk 1.5gb-EBR1: 2 sectors, 1024 bytes
Logical sector size: 512 bytes

Disk identifier (GUID): 42E75C31-9EF0-47FB-9C59-97DA9BE821CA
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 18446744073709551584
Partitions will be aligned on 512-sector boundaries
Total free space is 18446744069412095424 sectors (8.0 ZiB)

Number Start (sector)    End (sector) Size       Code Name
   1         1443328         2213375   376.0 MiB   8300 Linux filesystem
   2         2213376         5228031   1.4 GiB     8300 Linux filesystem
   3         5228032      4298899454   2.0 TiB     8300 Linux filesystem

You will now have new values:

The new values are now higher, make sure, as mentioned earlier, that partition two's End Sector is one digit less then partition three's start sector. Also make sure that no other values have changed from your original EBR1.

Now the fun part, restarting and logging back into windows so that you can access SPFlash tools, yes I know it really sucks!

Fire up SPflash tools, make sure you have selected the correct scatter.txt. When flashing your new EBR1 you are going to need to reflash everything, the new EBR1 is going to erase everything on your phone, which is why a backup and a second backup is very important.

In SPFlash you will see to your right, the location of your original EBR1, click that box on the right as shown below:

A window is now going to open, select your new 1.5gb-EBR1 and flash away!

**NOTE** At the time, am working on a mod that will allow you to extend your storage that will extend to your SDCARD. Have not tried the theory yet, but think that if you extend your EBR1 beyond the total space of your phone storage, for example, if you have 2.5gb of extra phone storage and want to add another 2gb, think it may work using the int2ext mod as shown on some forums.

Downside to this mod, you will not be able to remove or if anything ever happens to your SDCard or your tablet may not boot up, will probably get stuck at the first logo. Another issue is that, this could potentially eat up your SDCard.

Another problem is that, in order for this mod to work, you will need to edit your vold.fstab and save it back to your tablet. Some tablets have the option to adb to your phone once it gets to the boot logo. If this is the case, after flashing the EBR1 you can plug the tablet into the USB port and adb pull /etc/vold.fstab, edit and adb push back.

If you are unable to adb shell at the boot logo, the only other option is to edit your system.img, save the vold.fstab and flash back along with your new EBR1. An easier way, after reflashing via SPFlash tools to recover the brick, as long as one did download, from the play store, a nandroid backup. The backup saves your system as a system.tar. Open the system.tar file, locate the vold.fstab in /etc/ edit it with an editor, repack to the tar. You could then flash the new EBR1, with all other backups in SPFlash tools, boot into recovery, then restore your tablet to the last settings using the nandroid backup.

As for the SDcard part to work, it may have to be formatted as fat32 or unallocated, this way the EBR1 will write the needed numbers to the area, bad news, you would have to figure out how to:

partition the sdcard off and get your vold.fstab to recognize the amount of leftover storage you want it to read as phone storage. The tablet may not recognize the remaining SDCARD storage as phone storage if formatted as unallocated. Also, the EBR1 may not be able to extend to storage that is already formatted as fat32, it works for the phone storage, just not sure about the SDCARD theory.
use the entire SDcard as extended app storage, then buy yourself one of those USB memory sticks, it can be plugged into the tablet's USB port and the other end into your PC's USB Port. Not sure how most of these tablets work with the USB stick method, probably is another vold.fstab issue.

How to install Dual Boot Android x86 on PC KitKat 4.4 RC2 without USB or CD

2014-08-11T15:36:00.002-04:00

Not that long ago after screwing up my android while fooling around with ZTE merit codes on my ZTE Z990g that was rooted with the ZTE avail, I screwed up my touchscreen calibration firmware and cannot figure out how to reinstall it, oops. After figuring out how to get my rooted devices to work with android screencast on my computer so that it could be accessed, I than proceeded to try different techniques to unroot my android to see if there was any way to get into FTM mode. Just for kicks, my SD card reader decided to take a dive, great, now I have an android, that is unrooted and can't do a thing until my new phone and new touchscreen comes in.

Anyways, while doing many searches on how to fix my issue while waiting, I discovered the world of installing the Android Operating system on the computer. My oh my, this is so cool, had to try it out. Well since Android is still in beta testing, it was unable to detect my my keyboard after getting past the "install to harddisk screen", grrr. Tried it in Virtual Machine, way to slow, sheesh, if one wanted to go back in time and get that nostalgic feeling of installing windows 98 on a 486, why not do just that. Okay so there had to be a way, and let me just say, it was easier than I thought. There are a few ways I discovered, that one would not find in a search but had to know what they where searching for, search for all those little pieces and put them together, so I did just that, got Android KitKat running on my Desktop computer. Now let me make it easier for you, in one Blog Post, just how to the same thing I did, without doing all those searches one how to do one thing only to have to put them all together.

There are a few ways this can be done, my preferable way is using a Linux operating system, since Android is a linux operating system, this technique is a little easier than if you are running Windows. If using windows, it is probably a better idea to just use the steps to create an ext4 format on a USB stick, setup your bios settings to boot to USB stick as first or second boot option.

For Ubuntu, things you will or may need:

Ubuntu or Xubuntu live CD, 14.04 is the latest stable release
Android x86 KitKat RC2 Iso
Some type of unzip tool to extract your android x86 ISO to your harddisk, winzip - extraction tool already available if Ubuntu is already installed.
Gparted - if you are already running Ubuntu and have a second hard disk or a area already partitioned off, then you can run the following commands:

sudo apt-get install gparted

sudo gparted

If Ubuntu is already installed and you do not want to redo everything, but just want to create a new partition, there are a few work arounds.

Follow the steps using a USB Stick from gparted.

Want mega space to run all kinds of Google Play APPS in AndroidX86 Kitkat but do not have any available partition, than a fresh install of Ubuntu is the best method.

You could partition off the hard disk that Ubuntu is installed from using the method below through the live CD, but this may give you messy run around, causing issues with your boot.

If you do decide to try to partition off your primary Windows or Ubuntu drive, from the Ubuntu Live CD:

a. run Ubuntu Live CD

b. unmount the linux-swap if Ubuntu

c. right click on the primary partition and resize

                       d. create a new primary partition from the unallocated space

                       e. format the partition, ext4 is usually the safest way to go for
                            any Linux based operating system.

                       f. this could potentially cause problems with the Ubuntu boot
                           afterwards, if so, follow these instructions to repair the boot.

As for using Gparted to partition off your Windows drive, not really sure, again, if in doubt use a USB stick.

Burn your Ubuntu ISO to a CD, DVD or USB per instructions on the Ubuntu download link above.

If you already have done the following Steps for installing Ubuntu/Xubuntu, skip down to the link below for instructions on how to manually install Android X86 below.

Part One - getting ready for Android X86 KitKat!

Make sure BIOS is setup to recognize the device you plan on using to Install Ubuntu from under boot options (USB or CD storage). Each computer is different so you will have to reference your motherboard manual to find your settings.

Insert your Xubuntu/Ubuntu CD/USB stick and turn on the PC, when finished loading, select Try Xubuntu/Ubuntu:


When Ubuntu shell loads, click on the menu and open up your terminal:

sudo gparted

Gparted will now open, this is where you can partition your harddisk to suit your needs. Lets say you have a 1.5 tb hard disk like me, this is how I setup my partitions. For a fresh new install, you will need to right click on any partitions that are used and delete them, right click and delete until all the partitions are combined into one large unallocated space.


Right click and delete unwanted partitions, you want to work with unallocated space. If resizing, right click the partition you want to resize, create an extended partition then create a new ext4 partition. This method is useful if dual-booting with windows.

Right Click on free space and create your an ext3 or ext4 partition, in the box that says "Free space following MiB" select how much you want to leave for whatever operating system or storage you are going to need following

Optional: I'll show you later how to create an emulated SDCARD for Kitkat

Right click and again in the "Free space following MiB" set a number, if using for storage label storage, if using for your other OS skip this step.

Right Click, select new and create an extended partition than just select OK do not change any numbers.

If your going to install windows just select OK no need to enter any values.

Right Click and create new in the new unallocated space, it will match the extended space above it, in "Free Space following MiB" enter a number for Linux Swap to match the amount of ram you have. If you have 4gb of ram, then in the space "Free Space following MiB" enter 4000 for 4gb. Under file system select ext 4 for Ubuntu or ntfs/fat32 for windows

Skip this step if going to install windows. Right click one last time and make your file system Linux Swap.

This is how your final result should look

Part Two: Setting up Android X86 4.4 without having to use the install method.

Right click on the Android-x86 and select "Extract Here"
Now you should see a folder with the same name as the Android-x86 ISO you just extracted.
In that folder all you need are the following four files:

initrd.img
ramdisk.img
kernel
system.sfs

Select just those four and copy them to the drive where android-x86 is going to run from and paste them into a folder called Android. In the newly created folder Android create another folder called data. The data structure should now be:

Android-x86

data

initrd.img

system.sfs

kernel
ramdisk.img

There is a system folder in the picture above, this is because on the first boot of Android-x86, a system folder will be created automatically.

Open up terminal and enter the code:

sudo nano /etc/grub.d/40_custom

This is the following you will see:

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.

At the bottom, enter the following:

<code>menuentry "Android-x86" {

set root='(hd0,X)'
Linux /Android/kernel quiet root=/dev/ram0 androidboot.hardware=generic_x86 acpi_sleep=s3_bios,s3_mode SDCARD=sda3 SRC=/Android
initrd /Android/initrd.img}
</code>

If you skipped the step for creating an emulated SDCARD, then just remove the line, SDCARD=sdaX. If you did create a partition to use an emulated SDCARD, then below in the following command, <code>sudo fdisk -l</code> identify that partition and replace X with the number, mine is sda3. As for the <code>set root='(hdX,X)'</code> this is determined as to which drive android is running from. In terminal shell enter:

sudo fdisk -l

and the output will be, this is mine:

   Device Boot      Start         End      Blocks   Id System
/dev/sda1   *        2048   204802047   102400000   83 Linux
/dev/sda2       204802048   307202047    51200000    7 HPFS/NTFS/exFAT
/dev/sda3       307202048 1906276351   799537152   83 Linux
/dev/sda4      1906278398 2930276351   511998977    5 Extended
/dev/sda5      1906278400 2912458087   503089844   83 Linux
/dev/sda6      2912460800 2930276351     8907776   82 Linux swap / Solaris

sda1 is where android is running from, so my format is - set root='(hd0,1).

Example

Hard Drive

sda = (hd0,0)

sda1 = (hd0,1)

sda2 = (hd0,2)

USB Stick

sdb = (hd1,0)

sdb1 = (hd1,1)

sdb2 = (hd1,2)

Now that you have created your menuentry for android, press

ctrl x

press enter

type the letter y for yes

press enter

Now in terminal type:

sudo update-grub

sudo reboot

In the Ubuntu boot menu you will see Android-X86 at the bottom, scroll down, hit enter, sit back and enjoy Android on your PC!

how to created an animated banner with hyperlinks for your Google Blog

2013-06-30T20:09:00.002-04:00

Before following this tutorial, you will need gimp, click here to download and install if you already have not done so.

Included is the html, a banner and free animated icons for download.

RIght Click and save image as to download

Animated Gif format
Animated XCF format (for use with gimp)

#HowToRecoverGmailPassword

2013-03-22T12:28:00.000-04:00

Finally, now that I have a new android phone, I can access my emails, blogs and other accounts.

After spending weeks, unsuccessfully contacting various "so called" phone support options,while trying to remember what my Google password, as well as After trudging through Google's numerorious online support pages, this one support page was helpful, although yor have to read the very last paragraph:
The questions we ask to verify your identity are intentionally difficult. Answer as many questions as possible, and make sure your answers are accurate. If you’re unsure about an answer, provide your best guess. It also helps to submit your answers from a computer you've used in the past .
What reason Google has for asking when a user started using calendar is completely useless. if answering the question on a new computer, because the old one died, probably will not work, unless, of course you remembered using Google calendar one day back in '08 to see what day your birthday fell on.
Lastnight, finally, I was successful in resetting my Google password. Since changing my password on my fiance's Pantec phone back in September, that was the computer needed to be able to successfully answer my security questions. Now if Google only made this simple little support information more easily available for those who, like myself, could potentially save hours of wasted time.
After answering the security question and entering five reguraly email address I corresponded with, correctly, twenty-seven times (no joke) only to receive one of the following two emails rejecting my attempts. UPIN doing the exact same thing on my fiance's phone, without changing any of my answers, the password recovery option finally worked. The kicker is, thinking it wouldn't work, I only answered the questions half assed regarding to people emailed frequently. Only entered one email and one google product that I knew was 100% correct.

How to take a self portrait picture with your cell phone, blackberry, iphone or any other digital camera device

2012-03-27T00:06:00.000-04:00

This is a pet peeve of mine whenever somebody takes a self portrait of themselves for Facebook. Do not ask me why it bugs me but here are simple instructions of how to take a picture of yourself with your digital camera device:

Here are two pictures taken of myself with my blackberry:

The Wrong Way

The Correct Way

Okay, bad pics but done in the same area with the same phone on the same day. When taking your picture you want to turn your phone the opposite way you normally would. While standing in front of a mirror, look at your reflection of your camera/phone's screen in the same mirror. Once you get good shot of yourself, snap the button and you now have a self portrait. Another way to remember is that you want a picture of yourself, not your mirror.

The Funny Way

How to make your Google Blog Title Animated - Upload large animated gifs

2012-03-26T12:01:00.001-04:00

Google Blogs now supports animated gif, which means now you are able to upload animation to your blog posts or import them from outside links. You can also create your own animated blog post title like the one done on my new business blog, Elizabeth's Digital Business Cards." Many sites do not support animated gifs beyond, at the most, three megabytes. What you can do though is upload an animated gif to a blog post and than link it to your blog title.

Here are the steps:

Create a new blog post
Upload your photo using the insert image button than add selected
Right click the photo in the compose mode of your blog post and copy image URL
Go to your blogger settings, select the header gadget and paste your link in the header tab, under the area that says: From the web. Paste an image URL below.

Note: You do not have to submit the blog post of your image for this to work but can actually save it as a draft. This trick actually uploads all photos to your picasa account, which is automatically obtained upon the creation of a Google account.

Add pop-up text to an embeded sound file in a Google Blog post

2012-02-25T01:24:00.001-05:00

Adding an embedded Wave file in a Google Blog can be fun and important but what about adding a little pizazz to it by showing pop up text along with the embedded media in your blog post at the same time. For example, you want your blog visitor to hear a particular song, what can be more useful than to have the artist name and title show up when the blog visitor clicks on the embedded media. Try it with mine below:

This is simply done by adding the following code while in HTML mode of your blog composer:

<embed width="250" height="50" autostart="false" loop="false" playcount="2" src="http://YOUR-PERSONAL-SOUNDFILE.wav" span title="YOUR OWN TEXT"></embed>

That's it, you are all set, ENJOY!

Note: Blogger is very fussy with some codes, such as this one. Once you are done editing this in HTML mode you will notice that upon going to compose mode and than back to HTML mode your wav will disappear.

Spice up your next blogpost - How to make any image animated on Google Blogs and websites!

2012-02-24T02:37:00.000-05:00

This tutorial is actually so easy you are going to wonder why you never thought of it yourself. All you need is an image and a scrolling marquee html and you now have an animated picture on your blog post or even on your Google Blog sidebar within the Javascript/HTML Gadget.

Here is the code:

<marquee><img src="http://yourimage.com></marquee>

Using an image of your own or one hosted from an outside website will work either way. Simply upload the image or copy and paste the site where the image is being hosted. Click on HTML at the top left while in compose mode of your Google Blog post and enter <marquee></marquee>.

Next while your mouse courser is in between <marquee></marquee> click on the image icon and choose one of the options below to upload your image to your Blog.

Add an image from your computer

Add another imageWe accept jpg, gif, bmp and png images, 8 MB maximum size

Or add an image from the web

Add another image

URL

Learn more about using web images

You can even take an animated *.gif, like the one below, and add extra animation to it. Just a quick note, for some reason animated *.gif images will not work hosted directly on a Google Blog. If you wish to use an animated gif, it needs to be hosted from a website that supports animated gifs.

Force readers to subscribe to your RSS with this cute subscribe now widget for blogger

2012-02-21T21:26:00.000-05:00

Below is the code to add the following Subscribe now with Twitter, Facebook, RSS and Google Plus Buttons. All you need to do is just copy and paste the code into a new Gadget change the highlighted text to your own information and you are set.

I have created another Subscribe now button, to get the code simply click the links below to view and even save the text documents. At the bottom of the code is the code for google circles, if you wish to remove it, just delete the section at the end of the document that says:
<script type="text/javascript">mbgc='f5f5f5';ww='320';mbc='cecece';bbc='3F79D5';bmobc='3b71c6';bbgc='4889F0';bmoc='3F79D5';bfc='FFFFFF';bmofc='ffffff';tlc='cecece';tc='6a6a6a';nc='6a6a6a';bc='6a6a6a';l='y';fs='16';fsb='13';bw='100';ff='4';pc='4889F0';b='s'; pid='108709237685683796184';</script><script type="text/javascript" src="http://widgetsplus.com/google_plus_widget.js"></script>

Coffee Cup Subscribe Now - Download

Button Subscribe Now - Download

3D Social Network Icon Subscribe Now - Download

Elizabeth's Blogger Wikis: Add a facebook login button to your blogger using html code

2012-02-19T23:30:00.003-05:00

Elizabeth's Blogger Wikis: Add a facebook login button to your blogger using html code - Simple method

People have been having issues with the above tutorial on adding a facebook login button to your Google Blog on Blogspot. After doing a little research and testing for myself, there is another way. If you are using a heavily scripted blog on blogspot then the above tutorial will not work and you will get one or both of the following errors:

An invalid API key was specified
A large ugly Facebook Logo Button

To fix this problem, unfortunately you are going to have to use the more difficult tutorial but the upside to this one is that there is logout button as well. As you can see from mine on the top left when you log into Facebook from my site it works and you will also notice the logout option.

Step 1: Search for the code below and add code in red.....final look will be


<html expr:dir='data:blog.languageDirection'
xmlns='http://www.w3.org/1999/xhtml'
xmlns:b='http://www.google.com/2005/gml/b'
xmlns:data='http://www.google.com/2005/gml/data'
xmlns:expr='http://www.google.com/2005/gml/expr'
xmlns:fb='http://www.facebook.com/2008/fbml'>

Step 2: Put the below code above </head>


<script src='http://static.ak.connect.facebook.com/js/api_lib/v0.4/FeatureLoader.js.php' type='text/javascript'/>

Step 3: Put this code above </body>


<script type='text/javascript'> 
FB.init("

YOUR_API_KEY_HERE

" , "");
</script>

To add your_api_key_here, click the above link to find out how to obtain an api_key.

Step 4: Save changes you are almost done!!

Adding Facebook Connect-->>

LOGIN BUTTON-
<fb:login-button autologoutlink="True" length="short" background="white" size="large"></fb:login-button>

PROFILE PICTURE-
<fb:profile-pic uid="loggedinuser" facebook-logo="true" linked="false"></fb:profile-pic>

USER NAME-
<fb:name uid="loggedinuser" useyou="false"/></fb:name>

Make an Adobe PDF file from any document or website in Ubuntu

2012-02-11T15:50:00.000-05:00

Adobe PDF files are supported widely among many websites, for filling in application, emailing documents and downloading manuals from various websites. When creating an Adobe document it also gives you that feeling of security that it will be safe, because unlike many documents that you may email or post on a website, it cannot be edited like a Word Document possibly can. There are ways of creating a Word Document by setting the correct write protection properties but with an Adobe PDF file, there is very little maintenance in protection you document, which is great for a beginner.

In Ubuntu/Linux there is an option where you can print to file, but unlike windows it has the option of printing a file as a PDF document. This feature is great when creating a Resume or maybe you would like to back up some emails for future reference. In this tutorial I am going to show you how to, with ease, create an Adobe PDF file through your gmail account.

Step One:
Go into your GMail account and open the email you wish to print.

Step Two:
Click on the print icon in the top right corner of the email

Step Three:
A new window will open and the print dialog box will automatically open. For other documents you can Click on File --> Print, the hot key would be ctrl+p

Step Four:
Select the option Print to file in the window as pictured below

Step Five:
Just below that you will see a box with Name and to the right of that you will have the option of selecting the radio box of either PDF or Postscript, select PDF.

Step Six:
Name your document, make sure that *.pdf file extension is included.

Step Seven:
Below the Name box is the default Save to folder, change that as necessary.

Click on the print button, you are finished converting your GMail email to an Adobe PDF File!

Add a Custom Google Search to your Google Blogpost

2012-02-04T02:45:00.000-05:00

Adding a Custom Google Search to a website/blog can bring in extra revenue with a Google Adsense Account. How it is used on your website/blog is the important part in earning revenue. This tutorial will show you how to add a Custom Google Search to your Google blogpost and to learn how to make more use of a custom Google Search and earn extra revenue with Google Ad in a blogpost, click here to read more.

Step 1:

Go to your Google Adsense Account

Step 2:
Click on the My Ads Tab

Step 3:
Now click the link that says Search on the left pane

Step 4:
On the top click the tab that says New Custom Search Engine and fill in the fields as you wish.

Step 5:
Select Save and Get code and a iframe window will open, select the code, copy and than in the google blogpost where you want the code paste the code while you are in HTML mode when editing the post and your search bar will look like this.

Try mine out and enjoy!

Free tip:

Do you like how the eyeballs look on each side of my search bar pointing? Once you have selected an image that suites your needs, add an image and than anchor each image on the left and right. To get them to fit on one line you may have to edit your Google Custom Search Engine size. Once you have the images anchored, one on the left and the other on the right, just drag them to each side of the search bar.

To do this just change the character size from 55 characters to more or less, depending on your needs.

How to put music on Google Blogger/Blogspot

2012-01-28T02:43:00.000-05:00

There are many ways of putting music on your Google Blogger/Blogspot and it's another fun easy way to draw more users to your site. My favorite is mixpod, which has been around for quite some time now. With mixpod is you can select from a few of their ready made skins or, a personal favorite of mine, is the MiniPod which lets you customize the skin with the option of using some select eyecandy designs. Mixpod has their own search engine, mostly YouTube approved videos/songs. If you are unable to find the video/song you are looking for you have the option to manually enter a YouTube URL and once approved MixPod allow you to add to your playlist, the approval usually takes about twenty-four hours.

Here are the instructions to adding music to your Google Blogger/Blogspot:

When done correctly the Music Player below will be your outcome. As you can see, you can also copy and paste the code right into a blogpost. This is a great idea when posting something and using music to get the artistic point across to the readers of your blog.

Music Playlist at MixPod.com

Free Resume Tip: Create an attractive Resume on #CapitalAreaHelpWanted.com

2012-01-26T23:43:00.000-05:00

When posting your resume on CapitalAreaHelpWanted.com to apply for jobs you have probably noticed how there are no options to create an attractive resume using bullets, underline and bold. There is actually a way around that when posting a resume on CapitalAreaHelpWanted.com's website, you can view how mine looks by clicking here to view it.

First, if you haven't already done so, is first create a resume using a word processing program, such as Microsft word or my personal favorite is LibreOffice Writer because it is free and you can save documents in *.doc Microsoft Word Format. Once you have completed your resume at the top click File --> Save As and than save as a HTML document, you will need to change the file type from the default output format to HTML. In the newer versions of word processing programs simply saving the resume as resume.html will also work.

Next open up your web browser and now on the menu bar you will need to go to File --> Open or use the shortcut/hotkey on your keyboard by pressing Ctrl+O. Now browse to where the resume is save and open it.

To view the HTML source code for a Web page using Internet Explorer 3.x and later, click Source on the View menu. To view the HTML source code for a Web page using Internet Explorer 2.x, and FireFox you can right-click the Web page, and then click View Source. FireFox's shortcut/hotkey is Ctrl+U on the keyboard. In the new window that has opened, go to Edit on the menu bar and choose the option select all, the shortcut/hotkey on your keyboard is Ctrl+A. Now go back to Edit on the menubar and choose Copy, the shortcut/hotkey on the keyboard is Ctrl+C.

Next go back to CapitalAreaHelpWanted.com and again you will need to go to the Edit on the menu bar and select Paste or use the shortcut/hotkey Ctrl+V.

*Note: When creating a resume on CapitalAreaHelpWanted.com you have to use their name and address format at the top, so on your resume do not copy and paste or make sure that you have removed the name, address and telephone number field of the resume, just paste in the body of the resume is all that is needed.

How to get the facebook developer's Like box to work with Google blogger

2012-01-15T22:51:00.002-05:00

To easily add a like box to your blogspot blog first you will need to create an app by going to the Facebook Developers website and clicking on the Get Started link to see their tutorial on creating your app. The reason you need an app is so that you can obtain your own unique AppID for any app that you would like to use on Facebook, such as, the Like Box, the Facebook login button and networked blogs. To make your personal like box go to the Like Box - Facebook Developers section.

Once you are done setting up your Like Box at the bottom where it says Get Code, you want to change it to the IFrame than copy that code. Next go to your blogger layout, add a new gadget, select the HTML/javascript and paste your code than save.

Click to enlarge

That is it, you are all done and you now have your own like box!

Add a facebook login button to your blogger using html code

2012-01-11T00:00:00.000-05:00

UPDATE This is an updated tutorial on how to add a FaceBook Login button to your Google Blog/blogger/blogspot. Since my last post there are a few things that can be done so that the login button shows either when you are going directly to your personal blog or viewing a post. The earlier bug was that the login button was not showing, this has to do with the first step for it to work correctly.

Step One

Create an FaceBook App on the Facebook Developers website. This step is pretty much an easy walk through. Below is an image of what you need to get your app working correctly. Once you create your Facebook app it does take a little while for it to work on the website/blog so be patient.

In the image below make note that the following fields need to be completed. This set-up is a basic format. Once you create the Facebook app, this will help to promote your website as well.

Click to Enlarge

Step Two

Now that your Facebook app is ready the rest is very easy. Go to the blogger design site and select the blog you wish to add the Facebook Login Button to.

Select the Layout button and add a new Gadget, scroll down the list and select the HTML/Javascript Gadget.

Step Three

In the window copy and paste the following code:

<div id="fb-root"></div>
<script>(function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) return;
js = d.createElement(s); js.id = id;
js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=CHANGE THIS TO YOUR PERSONAL APP ID TO YOUR OWN PERSONAL ID LIKE THE ONE IN THE IMAGE ABOVE, JUST ABOVE THE SECRET KEY";
fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));</script><div class="fb-login-button" data-show-faces="true" data-width="200" data-max-rows="1"></div>

Click Save and you are done!

IMPORTANT: An issue that many of you will come across is:

An invalid API key was specified.

If you read this post prior, it was incorrect. The reason you will get this error is when you are using the Facebook Login button on a heavily scripted blog. Another issue is that you will see a big annoying Facebook logo in place of the login button on your blog, the fix to this is to either go and find what the conflicting problem in the HTML of your blog that is causing this error or just back up your blogger template and than select one of the Google Blogspot templates offered.

After doing this myself the error disappeared and the login button works great and Blogger does have some very nice templates now.

UPDATE: I have posted a more difficult tutorial for those who are running into the above problem. Another common problem with the heavily scripted blogs is you will see a big ugly Facebook Logo instead of the nice login button like mine on the top left sidepane.

Add a login button to your google blog - More technical method with better results

Google and Android tips tricks and hacks

Install Kodi on Amazon Firestick

Jailbreak Amazon Firestick

Thats it, enjoy Kodi on your firestick!

Installing Android-x86 4.4 and/or 5.1 on your desktop - PART #2

Unroot and Unbrick LG G Pad V410 AT&T Tablet back to stock

Making cellphone calls on a 4G LTE android tablet

Increase/Decrease MTK6572 Cache

Update: Tutoial Re-partition the MTK6572

Tutorial: How to repartition and increase app space MTK6582

Tutorial #2: Increase MTK6572 Data/Application Storage- Editing MTK6572 Scatter.txt

Part Two - Editing Scatter File and Increasing Phone/Tablet Speed

How to unbrick and unlock the ZTE Mert straighttalk/tracfone z990g to AT&T z990

*** WARNING I WILL NOT BE RESPONSIBLE IF YOU BRICK YOU PHONE PERMANENTLY - PROCEED AT YOUR OWN RISK ***

Sim unlocking the Merit/Avail to any carrier

Tutorial: How to increase partition on MediaTek Tablets MTK6572, MTK6577 and others

How to install Dual Boot Android x86 on PC KitKat 4.4 RC2 without USB or CD

Part One - getting ready for Android X86 KitKat!

how to created an animated banner with hyperlinks for your Google Blog

#HowToRecoverGmailPassword

How to take a self portrait picture with your cell phone, blackberry, iphone or any other digital camera device

How to make your Google Blog Title Animated - Upload large animated gifs

Add pop-up text to an embeded sound file in a Google Blog post

Spice up your next blogpost - How to make any image animated on Google Blogs and websites!

Add an image from your computer

Or add an image from the web

Force readers to subscribe to your RSS with this cute subscribe now widget for blogger

Elizabeth's Blogger Wikis: Add a facebook login button to your blogger using html code

Make an Adobe PDF file from any document or website in Ubuntu

Add a Custom Google Search to your Google Blogpost

How to put music on Google Blogger/Blogspot

Free Resume Tip: Create an attractive Resume on #CapitalAreaHelpWanted.com

How to get the facebook developer's Like box to work with Google blogger

Add a facebook login button to your blogger using html code

* WARNING I WILL NOT BE RESPONSIBLE IF YOU BRICK YOU PHONE PERMANENTLY - PROCEED AT YOUR OWN RISK *