Feedburner Facebook youtube pinterest twitter

Monday, September 1, 2014

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

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.


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.
  • 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:

  1. 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.
  2. 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.


  1. Hi, i was wondering if i can do this kind of procedure with a lenovo a706. Please i need some help. Thanks!

  2. Hola, tengo un avvio 793 porafavor ayudame a root para súper usuario, intente con root master y no funciona es un android 4.4.2 kikat, procesador mtk 6572 el cual al parecer fueron corregidos los agujero de seguridad por lo cual No funciona framaroot, vroot , kingroot z4root ,gingerbreak , towertool one click root , unlockroot,flash tool, mtkdroid,genius, y otras con las cuales no tuve éxito, pero incluso funcionan para otros avvios menos y mas avanzados y para todo tipo de dispositivos... me podrías ayudar con el root de mi avvio 793 y muchas gracias por la atención prestada... Espero tu pronta respuesta ;D

  3. I have a problem concerning the internal memory i have samsung galaxy s5 sm-G900 mtk6572 16 GB, after unbrickinga shows me that the memory consumption around 14 GB and the free 1 GB I do not know how to solve this problem right can help

  4. Please teach me how to increase System Partition:-
    I want to increase 1.5GB.
    Please help me..Thank you!

    1. yeayyy..i've found my self how to do that..Thnkz for the info above..

  5. pls make a flashble zip file...... what i can flash by twrp.....i got a zip file for my sony c203 and i got result....pls....do me a favour....

    1. I thnk mbr & ebr can't flash by recovery. U hv to flash using spflashtool. I'm not sure. Just fyi.

    2. This comment has been removed by the author.

  6. Can u help on irulu expro x11 I can't save any apps to ext SD card

  7. Can u help on irulu expro x11 I can't save any apps to ext SD card

  8. I always enjoy reading posts from this site.

  9. At first I doubted if this procedure would work but I'm happy o say that it actually just worked fine for me. I will keep on visiting this site for more of such reliable posts. Allow professional writers to assist you in writing your speech by simply clicking on this link: Best Way to End a Speech Presentation

  10. Oh no... :-) Such interesting method of counting partition sizes and boundaries :-)
    Do you hear something about Little-Endian and Big-Endian encoding?...

    "C6 31" is CANNOT be treated as 0xC631 in this case, and adding (decimal) 3*10 is NOT right nor exact method to increase 512MiB to 3*512MiB.
    "C6 31" is really must be taken as "00 C6 31 00" and treated as 0x0031c600 (=‭3261952‬ in decimal). So you must read whole hex number in 4 bytes from right to left by bytes (by two digits).
    For example (see next string in EBR1), "39 CE" have to be read as "FF 39 CE FF" and this is stands for 0xffce39ff, which is ‭4291705343‬ in decimal, which is length/size of last partition in sectors. You can easily check it by sum this length with last sector of previous partition (3261951) - you'd expect to logically get the last sector of counted partition. And yes, you will get 4294967294.

    And *PAY ATTENTION* this is the 1-before-the-last accountable sector in given 2TiB disk space in address space of 32-bit CPU architecture. It effectively means, that number more than 4294967295 is wrong. And... in your text you suggests to write down 4298899454... You could say "It's work though"? Of course, because you had never chance even be close to really write to such address on 4GB tablet... :-)

    Count with me. In original EBR1 the last sector of the last partition is marked as 4298899454. The next sector (the last one in address space), No 4294967295, is reserved (BOT for possibility of "final partition", beginning at 0xffffffff with 1 byte size). Sectors are numbered not from 1, but from 0. So, there is totally 4294967295+1=4294967296 sectors. 1 sector stands for 512b. So, we can address 4294967296*512=‭2199023255552‬ bytes. This is ‭2199023255552‬/1024 KiB, ‭2199023255552‬/1024/1024 MiB, ‭2199023255552‬/1024/1024/1024 GiB..... This is EXACTLY 2TiB, which can be physically addressed with 4294967296 sectors.

    BTW, you can see there, that partition sizes gdisk showed is for sure rounded, and size of last original partition (4294967294 - 3261951 = 4291705343 sectors = 2197353135616 bytes = 2046,44458 MiB) is NOT mentioned 2TiB (= 2048 MiB).

    Well, why we have exactly 4294967296 sectors in this system, and why I claim there cannot be more?
    Because, as I told before, we have 32-bit memory address space architecture, and sectors are counting in this number space. 1-bit stands for 0 and 1 (only 1 binary position), 2 possible digit/address space. 2-bit: 2 binary position, digits from 00 to 11 (from 0 to 3 in decimal) - 4 digit space (max. decimal digit + 1). Well 32-bit space stands for 8 groups of 4 sequenced 1 in row as maximal countable number, or x37777777777 in octal, or 0xffffffff in hex, or.... ta-daaaaa: 4294967295 in decimal :-) So, as I stated right above, maximum accountable (in this system) number is this number + 1, and there are our 4294967296 in decimal :-)

    Next, you actually have NO POSSIBILITY to assure that first sector of some partition = last sector of previous + 1, because it is computed automatically ;-)
    Please notice that we have encoded only the number of the first sector of an partition in EBR1 - and no trace of number of the last sector of the previous partition in EBR1 file. For example "06 16" (two lines up from marked "C6 31") stands for 0x160600 = ‭1443328‬ in decimal. Please compare it with gdisk output ;-)

    If you want to have 1.5GiB partition, you have to:
    1. Change "00 10" to "00 30", NOT to "00 2E"
    2. Change "C6 31" to "C6 51", NOT to "C6 4F"
    3. Change "39 CE" to "39 AE", NOT to "39 EC" (breaking system boundaries)

    Well... you should make some correction in your, in other, great work.

    Thank you once more for your effort and explanation of EBR1 table structure.


    1. Can we link this Informations here to other Forums Like hovatek, or xda developers?

    2. This comment has been removed by the author.

  11. Hello Vladimir,
    I am So happy to finaly found this forum, Mi cuestion: you can

    help me With mi Phone, i have te stockrom, and i want to resize Mi partitons to.... Best regards



My Blog List