Backup console

Inside the console NAND chip we can find 15 partitions + a parameter file (which stores the info about each partition position inside NAND chip); those partitions are the following ones:

loader (!!! NEVER NEVER NEVER PLAY WITH THIS PARTITION !!! DO NOT TRY TO FLASH IT IF YOUR CONSOLE IS WORKING FINE !)
rknand_uboot
rknand_misc
rknand_baseparamer
rknand_resource
rknand_kernel
rknand_boot
rknand_recovery
(almost unuseful because it does not contain any runnable executable)
rknand_backup
rknand_cache
rknand_userdata
(mounted ad /data/data/)
rknand_metadata
rknand_kpanic
rknand_system
(mounted as /system/)
rknand_user
(mounted as /mnt/internal_sd/)

Loader cannot be dumped but can be flashed (if you need them you can find them using google);
To have a working backup we need to backup the next 13 partitions, the last one (rknand_user - that is to say the external SD card
mounted at /mnt/internal_sd/), is not needed, anyway I will write how to dump it if you want to.

You will need 2 tools:

1 - RK_Android_Tool_2.3.9
2 - RK Rom Dumper and Flasher for Windows

Download drivers_tools.rar

the 1st one is used to put the console in USB-Download Mode (and to flash already dumped partitions also)
the 2nd one is used to dump partitions

we need to use both of them because the 1st one seems to have a bug which sometimes produces bad dumps dealing with big partitions


PROCEDURE:


* WARNING WARNING WARNING WARNING WARNING *

IF YOU PRESS THE “LOWER FORMAT” BUTTON INSIDE ANY OF THE PROVIDED DUMPING/FLASHING
TOOLS YOU WILL ERASE ALL PARTITIONS ! DO NOT PRESS IT UNLESS YOU HAVE A FULL
BACKUP OF YOUR NAND !! IF YOU HAVE IT YOU CAN RECOVER EVERYTHING BUT IF YOU DO NOT HAVE IT ABSOLUTELY DO NOT PRESS THAT BUTTON !!!!

IF, IN ANY CASE, YOU MANAGED TO DAMAGE YOUR CONSOLE TRY TO USE THIS STOCK FIRMWARE TO TRY TO RECOVER IT (flash ALL partitions with ROM_Dumper_Tool.exe renaming parameter.txt to parameter. ): https://mega.nz/#!bg9wVR5J!thSs92YW1jNGH5ayh_EIDxUC_yNkCFyhuEgyHhcrs-Q
IN THIS CASE YOU DO NOT NEED loader PARTITION.

1 - Connect the console to the USB (it will automatically power on).
2 - Install the appropriate ADB drivers;
3 - Now open AndroidTool.exe: if ADB driver is correctly installed you will see “Found One ADB Device” at bottom;
if so press the “Switch” button, the console screen will get black and it will reboot in Download Mode; now Windows will find a new device connected (the USB-Download Mode one): feed it with correct drivers; now the text “Found one LOADER Device” will appear
at bottom. If “No Device Found” it means you lack ADB and/or USB-Download Mode drivers.
(NOTE: to dump partitions we don't need MTP drivers, we will need them later to copy games from PC to device internal SD card)
5 - Now that the USB-Download Mode is correctly identified select the “Advanced Functions” tab and write the following in “Export Image” Button fields:
Start: 0
Count: 2
(leave “LBA” unchecked) and press “Export Image” button; it means “start reading from 0 for 2 blocks” (each block = 512 bytes); it will produce \Output\ExportImage.img;
6 - Now rename ExportImage.img to parameter.txt and open it Windows notepad (make sure format → wrap is checked inside notepad options).
7 - the first line is something like this:
PARMø FIRMWARE_VER:4.4.4:
delete the “junk” in front of the word FIRMWARE so it looks like this now:
FIRMWARE_VER:4.1.1
8 - at the end of the file you will see this word:
(user)
and after it there will be some other junk: delete everything after (user) including any blank space.
9 - when done make sure to hit ENTER once so there is a new line after (user)
10 - save the file leaving it open as we need data from it to continue.
11 - close RK_Android_Tool_2.3.9 and open \RK Rom Dumper and Flasher for Windows\

1 - Inside RK Rom Dumper and Flasher for Windows go to “Advanced Function” tab and now you need to manually insert data in Start and Count fileds as you did
to export the parameters partition reading them form the parameter.txt itself; so if you have for example: 0x000C8000@0x000F2000(system) you need to put
0x000F2000 (the part AFTER the @) in “Start”
and
0x000C8000@ (the part BEFORE the @) in “count”
(remember to put 0x in front of the values, just like in the above example)
and hit the “ExportImage” button; the partition will be always dumped in \Output\ExportImage.img folder, REMEMBER TO RENAME THE FILE EACH TIME WITH THE APPROPRIATE NAME (ex. uboot.img, system.img, etc) otherwise the next partition wil be overwritten !
do this for ALL partition listed (usually the 1st one is 0x00002000@0x00002000(uboot) ) and you will have your firmware backed up !
2 - OPTIONAL: Now to dump also the user partition you should do some math but this is not needed if the memory chip is the same as mine;
if, at the end of the parameter.txt you have the following values:
…..0x000C8000@0x000F2000(system),-@0x001BA000(user) it is like mine !
it means that (user) partition starts at 0x001BA000 and the “-” before the @ mens it doesn't know how big is it ! If you have a 4GB chip the “count” value will be 0xD2C00000; to see if it is a 4GB chip click the “ReadFlashInfo button and on “Flash Size” you should read: 4256MB:

if so use the above value, if not you need to do some extra maths: using Windows Calculator set in Programmer's mode you need to add the 2 values of last partition (in our example 000C8000 and 000F2000) and subtract them form the whole size (in hexadecimal value!) of your nand chip (ex.for a 2GB chip the total number of bytes will be 80000000, which, divided by 512 makes 400000 so you need to do: 400000 - (000C8000+000F2000) = 00400000 - 001BA000 = 246000. So for (user) partition “Start” will be:0x001BA000 while “Count” will be 0x00246000.
3 - If you want to permanently add that value substitute, inside parameter.txt, the ” - “ in -@0x001BA000(user) with 0x00246000@0x001BA000 or whathever the value is and save !
4 - Store all the dumped files in a secure place :)

DONE !


Files:
drivers_tools.rar

You could leave a comment if you were logged in.