Android Tablets Forum banner
1 - 2 of 2 Posts

Super Moderator
1,192 Posts
Discussion Starter · #1 ·
A set of batch scripts for dumping, writing, erasing and unbricking.
Use these scripts at your own risk - no guarantee of any kind.

Download :

Batch file names:


USB Dumper + Tools Package for AML8726mx by cxz

A set of batch scripts for dumping, writing, erasing and unbricking.
Use these scripts at your own risk - no guarantee of any kind.

Uses the update.exe from the Amlogic USB Burning Tool.
(older update.exe version is used because the newer ones freezes.)

Dumping partitions
(when recovery and/or system doesn't boot.)

1. Connect USB cable.
2. Start the device while keeping Power and Volume- buttons down.
(Some tablets it can be Power and Home that works instead.
Try different combinations.)

If the "WorldCup Device" is not under "libusb-win32 devices"
in device manager you have to install the driver in the
"AmlogicusbBurningdriver" folder. (Tip. A good usb-tool
is "USBDeview" by Nir Sofer.

3. Run DUMP-partitions.bat batch file.
4. Answer "y" when asked. Use enter to skip.

With DUMP-offset-or-full.bat one can possibly save some
data if partitions cannot be dumped. (The bad blocks are
not checked.) It's a good idea to check dumped files with
a hex editor.

The reading data is quite slow because of the update tool.
If you have a custom uImage_recovery/recovery.img file you
can use COMMAND-boot-uImage---drop_file_here to boot it.
After that use it (+adb) and do backing up/dumping faster.
e.g: adb pull /dev/mtd/mtd0 (where 0 is the partition number)

The dumped ~environment-for-dumper.bin is not for editing.
The batch only use it for finding out the partitioning.
Use DUMP-environment.bat to save the environment used.

To write dumps back in the partitions must exist and
they must be erased empty.

There is also some other batch files included.
They do NOT proceed without asking a permission.

Super Moderator
1,192 Posts
Added just some examples how to use some of the bat files. No need to re-download the text is below.

How to start recovery to flash a firmware

If the bootloader is on NAND (COMMAND-check-connection.bat)
just use the COMMAND-boot-uImage---drop_file_here.bat

If the bootloader is not on NAND run following bat
(bootloader.img must be in the bat's folder)

At this point wiping the device is usually needed, so use
WIPE-scrub-the-device.bat (or WIPE-erase-the-device.bat)
to do that.

After that you can write the bootloader to NAND

The COMMAND-boot-uImage---drop_file_here.bat
should work now.

Now you should be able to flash the firmware zip
that is meant for the device. Remember to wipe
data/cache/media (using normal recovery mode).

How to write recovery to NAND
After the bootloader is in its place you can
use WRITE-partition-file-to-nand---drop_file_here.bat
to write recovery, boot etc. to NAND,
but that isn't normally needed if you have a working
firmware zip available.

In many firmwares the recovery is in "recovery"
folder having "recovery-from-boot.p" as its name.
Use FILES-recovery-from-boot.p-to-recovery.img.bat
to convert it to correct (stock) recovery.
The file size of recovery-from-boot.p should be about as
big as the boot.img. If much smaller it could be just
a patch and it cannot be used.

In sd card update packages the "u-boot.bin" file is usually
the same as "bootloader.img" so it can be used if "bootloader.img"
is missing for some odd reason.

If after updating the device keeps on booting from the sd card try
using COMMAND-environment-reset-to-update-done.bat. It should fix it.
1 - 2 of 2 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.