how make livesuite.img with dumped rom.

[snakekiller]

can somebody explain it please.
with a tutorial or something.
i found how i dump the rom.
from my yarvik tab364.
but what can you do with the files.
and how repack it to a livesuite.img.

[sabercatpuck]

Quick go at it

http://www.freaktab.com/showthread.p...-Rom-(PMID701C)


1) get the A10Kitchen

http://forum.xda-developers.com/showthread.php?t=1490886

2) if you have not gotten ADB set up, you will need it.

3) use this command :
dd if=/dev/block/nand_ of=/mnt/extern_sd/____.fex bs=4096
to get the recovery, root, and system directories for your tablet, these will be placed in the _input directory

4) adb shell
su
mkdir nanda
mount -t vfat dev/block/nanda /nanda
Ctrl -c to exit
adb pull /nanda
this gets coppied into the _bootfs directory

then type create_image in cmd

This is the quick version, got an appointment so have to run


This stuff is from Shaun:
PMID701 Series INFO

By pressing the menu button while the tablet is off and hold it while plugging into a pc, FEL mode is activated allowing Live Suite to flash roms.

Partition Tables
/dev/block/NAND_

Gingerbread ICS

0 NANDA = BOOT 0 NANDA = BOOTLOADER
1 NANDB = ROOT 1 NANDB = ENVIRONMENT
2 NANDC = SYSTEM 2 NANDC = BOOT\KERNEL
3 NANDD = DATA 3 NANDD = SYSTEM
4 NANDE = MISC 4 NANDE = DATA
5 NANDF = RECOVERY 5 NANDF = MISC
6 NANDG = CACHE 6 NANDG = RECOVERY
7 NANDH = N/A 7 NANDH = CACHE

Permissions
rw-r--r-- /system/app
rwxr--r-- /system/preinstall

Gingerbread Kernel Location ICS Kernel Location
bImage - boot.img\linux\bImage u-boot.bin - boot.img\linux\u-boot.bin

Commands

Boot Recovery Command
adb shell "echo -n boot-recovery | busybox dd of=/dev/block/nande count=1 conv=sync; sync; reboot"

Mount Command
mount *.img -o loop /dir/

Dumping Command
dd if=/dev/block/nand_ of=/mnt/extern_sd/____.img bs=4096

http://www.freaktab.com/forumdisplay...laroid-Tablets
http://www.freaktab.com/showthread.p...wn-Photo-Shoot
http://rhombus-tech.net/allwinner_a10/a10_boot_process/
http://www.slatedroid.com/topic/2894...gure-this-out/

[snakekiller]

ok thx i try it when i have my tablet back from factory for repair.
thats about a big 2 weeks.
i let you now.

sent from my samsung galaxy gio with tapatalk

[shawnbusker]

Snake, if you pm me I can send you a script to simplify the dumping of the nand files and creation of the livesuite image.

Shawn

[snakekiller]

hello shawn
have you send the script to me already? because my wife read the mails too and maybe she deleted already accidentally.

Verstuurd van mijn GT-S5660 met Tapatalk

[Lexridge]

3) use this command :
dd if=/dev/block/nand_ of=/mnt/extern_sd/____.fex bs=4096
to get the recovery, root, and system directories for your tablet, these will be placed in the _input directory

Okay, now for a stupid question. You say get the recovery, root and system. Which is root? Bootloader or Boot/Kernel, or neither?

EDIT: Nevermind, I figured it out.

[sabercatpuck]

Haven't done it much myself

Okay, now for a stupid question. You say get the recovery, root and system. Which is root? Bootloader or Boot/Kernel, or neither?

I was just trying to consolodate stuff I had been through for the most part. I have not done a from the beginning build of this (though I was thinking I might when I get a chance just to make a verson that sets Debug mode on right from the flash) but my understandng is it is this way:
GingerBread:
NandA-Boot
NandB-Root
NandC-System
NandF-Recovery

ICS
NandA-Boot
NandC-Root
NandD-System
NandG-Recovery

Root, System, and Recovery are handled as complete images, where the Boot (NandA) is dealt with as a complete downloaded FAT filesystem directory and dealt with in the compressing routine. As a heads up, it takes about 2-3 times as long to uncompress the flashable image as it does to compress it.
The NandA informtion is fairly easy to work with since it is a FAT image, though if you want to modify the Script.bin file to change options (redirect the serial console to the SD card for instance) then you may need Linux. The script and script2fex tools needed to make the alterations are in scripts. There have been some C code versions released but as yet I have not seen them ported to Windows and I did not have good luck trying to run the scripts in a ruby or perl environment in windows.
If you want to try to manipulate the Root, System and Recovery images extracted from the factory ROM you need the Simg2img tool. They use a sparse image to save space.

You can see here for some other info on the simg2img use:

http://android2me.blogspot.com/2012/05/unpack-modify-and-repack-a10-image-file.html

[Lexridge]

It is looking like I have to have a ORIGINAL firmware image for my tablet before I can do this, and until I have one, I am dead in the water with this. Damn!

I was just trying to consolodate stuff I had been through for the most part. I have not done a from the beginning build of this (though I was thinking I might when I get a chance just to make a verson that sets Debug mode on right from the flash) but my understandng is it is this way:
GingerBread:
NandA-Boot
NandB-Root
NandC-System
NandF-Recovery

ICS
NandA-Boot
NandC-Root
NandD-System
NandG-Recovery

Root, System, and Recovery are handled as complete images, where the Boot (NandA) is dealt with as a complete downloaded FAT filesystem directory and dealt with in the compressing routine. As a heads up, it takes about 2-3 times as long to uncompress the flashable image as it does to compress it.
The NandA informtion is fairly easy to work with since it is a FAT image, though if you want to modify the Script.bin file to change options (redirect the serial console to the SD card for instance) then you may need Linux. The script and script2fex tools needed to make the alterations are in scripts. There have been some C code versions released but as yet I have not seen them ported to Windows and I did not have good luck trying to run the scripts in a ruby or perl environment in windows.
If you want to try to manipulate the Root, System and Recovery images extracted from the factory ROM you need the Simg2img tool. They use a sparse image to save space.

You can see here for some other info on the simg2img use:
http://android2me.blogspot.com/2012/...mage-file.html

[Lexridge]

It is looking like I have to have a ORIGINAL firmware image for my tablet before I can do this, and until I have one, I am dead in the water with this. Damn!

Here is how far I got using VirtualBox running on Fedora 14 with a 32bit Windows 7 installed.

1. I have my rootfs (from nanda) file structure extracted to the _rootfs folder.

2. I have system.fex, recovery.fex and root.fex in the _input directory

3. I have extracted the script.bin file to script.fex, but I was not sure if there was really anything I needed to modify there, except maybe cpu speed from 1008 to 1200, which I didn't

4. Ran create_image.bat. Got a missing file error, but it was mostly gibberish, and I have no idea what it was trying to tell me. This is the readable part of the error: ...\_extract\\COMMON_SYS_CONFIG000000.fex. Now, on the windows machine doing the same thing, it goes a bit further and errors out on RFSFAT16_OEM_000000000000.fex. It did however create some very small files in _output. The largest being bootfs.fex at 5133KB.

From reading one of the links here on how to build Allwinner from souce, it said I needed a original firmware, named original.img. In the above Step 4 I tried using the Polaroid 701i.img file, renamed, and it told me that this program will not work on a virtual machine.

So, I moved it all to my laptop which runs Windows 7 64bit, with pretty much the same results.

I was able to extract the 701is img file just fine. However, since this is not the ROM I am needing an image of, all I did was prove that much really works on real windows, but the files are pretty much useless to me, I think.

Am I missing something here sabercatpuck? Surely there is a way to do this without having the original firmware image. Somebody here did it for the Polaroid, did they not?
Finless, care to chime in?

thanks

[sabercatpuck]

Short answer is the important step you didn't mention was extracting an image of similar vintage (GB or ICS). You need the files in there to make a new flashable image.

Now for the Long answer:

First all of the high level ROM image tools where you are extracting and creating the flashable image is done in Windows. Editing the embeded system, root, recovery images is done in Linux (the current recomended one for building from scratch is Ubuntu 10.04).
I know that it is possible to use a different version of an image to then create a new flashable image that does work. Many of the files included in the flashable image are really small programs that are loaded into the memory of the tablet while it is flashing, and actually are not part of the information that is actually flashed onto the ROM, they just do the work. The system relies on a special section of code, embeded into the AllWinner microprocessor itself, called FEL. FEL is just a very simple boot over USB program that is kicked in under certain circumstances. (There is work well underway to reverse engineer the process to help make an open source version of LiveSuite eventually).
As such it is possible to make a flashable ROM for your unit out of one that was just similar to what you need. That is how Shawn made the first gingerbread ROM for the PMID701C. He was able to use the support programs found inside the Onda GB firmware coupled with the images he pulled from the tablet itself to make a bootable. That is why the first step in the process is to extract the image from a flashable ROM of similar vintage (it is even possible that it only needs to be a GingerBread or ICS from any of them, though I cant say for sure). That gets all of the small loader programs out into the extract folder where it looks for them later. Now the big thing that sets the A10 kitchen up, is that he changes a file (I am not at my PC so I cant track down the specifics of it at the moment) which you could call the recipe for cooking the ROM. In it he redirects where the root, recovery and system files are pulled from, while still pulling the rest of them from the original extract folder. The NANDA partition in the bootfs folder are also encoded seperately before being inserted into the final image mix.

So the quick steps are:
1) be sure you know and use the right kitchen for GB or ICS, the files included are slightly different
2) put an original GB or ICS flashable image into the appropriate directory and run (in windows)extract_image.bat to get all the support files into the _extract directory
3) extract the NANDA partition to the _bootfs directory
3) extract the ROOT, RECOVERY, and SYSTEM.FEX files into the _input directory
4) in Windows run the create_image.bat file to make the flashable image
5) use LiveSuite to flash the output.img file to the tablet

As a proof of concept, you should be able to extract the original image, copy the ROOT, RECOVERY, and SYSTEM files now in the _extract folder to the _input folder and change the longer names to the simple ones it will be looking for, and as long as you have a valid NANDA in the _bootfs directory it will create a full valid flashable image. Just dont do like I did once and have a second copy of bImage in there, it makes the resulting file too big and when it goes to flash it looks like it is going OK, only to have the counter suddenly drop back to zero and the flash fail.

One question what tablet and OS are you working on just for curiosity?

Also in reality if you are just making a system that is a new flashable ROM to backup your system (as we were doing before Polaroid finally put their stock ROMS out on their website) then you would not even need to get into Linux, it would all be done from Windows. Linux is only needed if you intend to start modifying the EXT4 images that we extracted from the tablet, and you wouldn't need that if you could come up with a clever way of mounting the images in Windows, but so far all of the tries to do that I have seen either just didn't work or are more complicated than setting up a dual boot or virtual Linux system.
(I do want to reiterate a caviat, I am trying to do all of this from memory so some details may be a bit off)

[Lexridge]

Short answer is the important step you didn't mention was extracting an image of similar vintage (GB or ICS). You need the files in there to make a new flashable image.

This was mostly the root (no pun intended) of my confusion. I didn't realize I could use a similar ROM file, and not the exact ROM file.

Many of the files included in the flashable image are really small programs that are loaded into the memory of the tablet while it is flashing, and actually are not part of the information that is actually flashed onto the ROM, they just do the work. The system relies on a special section of code, embeded into the AllWinner microprocessor itself, called FEL. FEL is just a very simple boot over USB program that is kicked in under certain circumstances.

This explains a lot. I actually wondered what was being used from the original.img that was so imperative to have. I assumed it was the boot filesystem.

That gets all of the small loader programs out into the extract folder where it looks for them later. Now the big thing that sets the A10 kitchen up, is that he changes a file (I am not at my PC so I cant track down the specifics of it at the moment) which you could call the recipe for cooking the ROM. In it he redirects where the root, recovery and system files are pulled from, while still pulling the rest of them from the original extract folder. The NANDA partition in the bootfs folder are also encoded seperately before being inserted into the final image mix.

I assume this is the script.bin file you refer to. I extracted it to a fex file, and looked at it, but I did not make any changes to it. I was not sure it needed anything changed.

So the quick steps are:
1) be sure you know and use the right kitchen for GB or ICS, the files included are slightly different
2) put an original GB or ICS flashable image into the appropriate directory and run (in windows)extract_image.bat to get all the support files into the _extract directory
3) extract the NANDA partition to the _bootfs directory
3) extract the ROOT, RECOVERY, and SYSTEM.FEX files into the _input directory
4) in Windows run the create_image.bat file to make the flashable image
5) use LiveSuite to flash the output.img file to the tablet

I was so close. As soon as I get home, I will continue working on this. All I need at this point is to get an img file into the _extract folder.

One question what tablet and OS are you working on just for curiosity?

The tablet is a Zeki TB782B A10 tablet with ICS 4.0.3 on it.

Also in reality if you are just making a system that is a new flashable ROM to backup your system (as we were doing before Polaroid finally put their stock ROMS out on their website) then you would not even need to get into Linux, it would all be done from Windows. Linux is only needed if you intend to start modifying the EXT4 images that we extracted from the tablet, and you wouldn't need that if you could come up with a clever way of mounting the images in Windows, but so far all of the tries to do that I have seen either just didn't work or are more complicated than setting up a dual boot or virtual Linux system.
(I do want to reiterate a caviat, I am trying to do all of this from memory so some details may be a bit off)

I just want a backup ROM for now, and after I get that, I certainly do want to start modifying it. I use Linux pretty much exclusively. I only keep Windows around in case I really need it.

Thanks so much for your time

[Lexridge]

okay, still, all is not well. Files that create_image.bat is looking for cannot be found. They simply are not belonging to the _extract directory. For instance, it does not create the RFSFAT16_BOOTFS_000000000.fex file. It also looks for a RFSFAT16_OEM_00000000000.fex file which I don't have.

Here is what I do have (and this has been the case when extracted four different ROMS so far, Polaroid 701i ICS and the Onda ICS to name two.
:
RFSFAT16_BOOT_00000000000.fex
RFSFAT16_BOOTLOADER_00000000000.fex
RFSFAT16_DISKFS_00000000000.fex
RFSFAT16_ENVIROMENT_00000000000.fex
RFSFAT16_RECOVERY_00000000000.fex
RFSFAT16_SYSTEM_00000000000.fex
RFSFAT16_VBOOT_00000000000.fex
RFSFAT16_VBOOTLOADER_00000000000.fex
RFSFAT16_VENVIROMENT_00000000000.fex
RFSFAT16_VRECOVERYFS_00000000000.fex
RFSFAT16_VSYSTEMFS_00000000000.fex

I will keep on reading and trying things. Thanks for all your help.

[sabercatpuck]

Here is some info

The file I was talking about in the other post is packer_ics/files/image.cfg. Here are the contents of the one I have. I think I may have deleted a line to fix one of the things you found too figuring if it wasn't in the one I had it might not have been needed. I can't recall if I have made an ICS one that I flashed though.

;/**************************************************************************/
;2010-06-09
;Sam
;image>ÅäÖÃÎļþÄÚÈÝ
;/**************************************************************************/
;maintype 8 byte string
[MAIN_TYPE]
ITEM_COMMON         = "COMMON  "
ITEM_INFO           = "INFO    "
ITEM_BOOTROM        = "BOOTROM "
ITEM_FES            = "FES     "
ITEM_FET            = "FET     "
ITEM_FED            = "FED     "
ITEM_FEX            = "FEX     "
ITEM_BOOT           = "BOOT    "
ITEM_ROOTFSFAT12    = "RFSFAT12"
ITEM_ROOTFSFAT16    = "RFSFAT16"
ITEM_ROOTFSFAT32    = "FFSFAT32"
ITEM_USERFSFAT12    = "UFSFAT12"
ITEM_USERFSFAT16    = "UFSFAT16"
ITEM_USERFSFAT32    = "UFSFAT32"
ITEM_PHOENIX_SCRIPT = "PXSCRIPT"
ITEM_PHOENIX_TOOLS  = "PXTOOLS "
ITEM_AUDIO_DSP      = "AUDIODSP"
ITEM_VIDEO_DSP      = "VIDEODSP"
ITEM_FONT           = "FONT    "
ITEM_FLASH_DRV      = "FLASHDRV"
ITEM_OS_CORE        = "OS_CORE "
ITEM_DRIVER         = "DRIVER  "
ITEM_PIC            = "PICTURE "
ITEM_AUDIO          = "AUDIO   "
ITEM_VIDEO          = "VIDEO   "
ITEM_APPLICATION    = "APP     "
;-->×ÓÀàÐ͸ñʽ£¬¹©²Î¿¼£¬¿ÉÒÔÁíÍⶨÒå
;-->max len  must be 16 byte.
[SUB_TYPE]
SUBTYPEdemo1 = "071228HWSXXXX100" --> hardware scan
;-->071228 2007-12-28
;-->HWS hardware scan
;-->XXXX Óû§¶¨Òå
;-->100 version 1.00
;·¾¶¶¨Òå
[DIR_DEF]
INPUT_DIR = ".\"
;--filename  ÎļþÃû³Æ
;--maintype ÎļþÖ÷ÀàÐÍ
;--subtype Îļþ×ÓÀàÐÍ
[FILELIST]
;//-------------¹«¹²²¿·Ö-----maintypeÓësubtype²»¿É¸Ä±ä--------------------------------------------------------------------------
;//-->¹Ì¶¨²»±äµÄ
    {filename = INPUT_DIR .. "_extract\\COMMON  _SYS_CONFIG000000.fex",        maintype = ITEM_COMMON, subtype = "SYS_CONFIG000000",},
    {filename = INPUT_DIR .. "_extract\\COMMON  _SYS_CONFIG100000.fex",        maintype = ITEM_COMMON, subtype = "SYS_CONFIG100000",},
    {filename = INPUT_DIR .. "_extract\\COMMON  _SPLIT_0000000000.fex",    maintype = ITEM_COMMON, subtype = "SPLIT_0000000000",},
    {filename = INPUT_DIR .. "_output\\bootfs.fex",           maintype = ITEM_ROOTFSFAT16, subtype = "BOOTLOADER_00000",},
    {filename = INPUT_DIR .. "_extract\\RFSFAT16_ENVIROMENT_00000.fex",           maintype = ITEM_ROOTFSFAT16, subtype = "ENVIROMENT_00000",},
    {filename = INPUT_DIR .. "_input\\root.fex",   maintype = ITEM_ROOTFSFAT16, subtype = "BOOT_00000000000",},
    {filename = INPUT_DIR .. "_input\\system.fex", maintype = ITEM_ROOTFSFAT16, subtype = "SYSTEM_000000000",},
    {filename = INPUT_DIR .. "_input\\recovery.fex",   maintype = ITEM_ROOTFSFAT16, subtype = "RECOVERY_0000000",},
    
    {filename = INPUT_DIR .. "_output\\vboot.fex",    maintype = ITEM_ROOTFSFAT16, subtype = "VBOOTLOADER_0000",},
    {filename = INPUT_DIR .. "_extract\\RFSFAT16_VENVIROMENT_0000.fex",           maintype = ITEM_ROOTFSFAT16, subtype = "VENVIROMENT_0000",},
    {filename = INPUT_DIR .. "_output\\vroot.fex",    maintype = ITEM_ROOTFSFAT16, subtype = "VBOOT_0000000000",},
    {filename = INPUT_DIR .. "_output\\vsystem.fex",    maintype = ITEM_ROOTFSFAT16, subtype = "VSYSTEMFS_000000",},
    {filename = INPUT_DIR .. "_output\\vrecovery.fex",   maintype = ITEM_ROOTFSFAT16, subtype = "VRECOVERYFS_0000",},
    
    {filename = INPUT_DIR .. "_extract\\BOOT    _BOOT0_0000000000.fex",             maintype = ITEM_BOOT,   subtype = "BOOT0_0000000000",},
    {filename = INPUT_DIR .. "_extract\\BOOT    _BOOT1_0000000000.fex",             maintype = ITEM_BOOT,   subtype = "BOOT1_0000000000",},
    {filename = INPUT_DIR .. "_extract\\PXTOOLS _xxxxxxxxxxxxxxxx.fex",            maintype = ITEM_PHOENIX_TOOLS, subtype = "xxxxxxxxxxxxxxxx",},
    {filename = INPUT_DIR .. "_extract\\FES     _FES_1-1000000000.fex",      maintype = ITEM_FES,    subtype = "FES_1-1000000000",},
    {filename = INPUT_DIR .. "_extract\\FES     _FES_1-2000000000.fex",      maintype = ITEM_FES,    subtype = "FES_1-2000000000",},
    {filename = INPUT_DIR .. "_extract\\FES     _FES_200000000000.fex",        maintype = ITEM_FES,    subtype = "FES_200000000000",},
    {filename = INPUT_DIR .. "_extract\\FES     _FES_000000000000.fex",          maintype = ITEM_FES,    subtype = "FES_000000000000",},
    {filename = INPUT_DIR .. "_extract\\FET     _HW_SCAN_00000000.fex",      maintype = ITEM_FET,    subtype = "HW_SCAN_00000000",},
    {filename = INPUT_DIR .. "_extract\\FET     _UPDATE_BOOT0_000.fex", maintype = ITEM_FET,    subtype = "UPDATE_BOOT0_000",},
    {filename = INPUT_DIR .. "_extract\\FET     _UPDATE_BOOT1_000.fex", maintype = ITEM_FET,    subtype = "UPDATE_BOOT1_000",},
    {filename = INPUT_DIR .. "_extract\\FET     _FET_RESTORE_0000.fex",  maintype = ITEM_FET,    subtype = "FET_RESTORE_0000",},
    {filename = INPUT_DIR .. "_extract\\FET     _MAGIC_CRC_START_.fex",   maintype = ITEM_FET,    subtype = "MAGIC_CRC_START_",},
    {filename = INPUT_DIR .. "_extract\\FET     _MAGIC_CRC_EN_000.fex",     maintype = ITEM_FET,    subtype = "MAGIC_CRC_EN_000",},
    {filename = INPUT_DIR .. "_extract\\FET     _MAGIC_DE_START_0.fex",   maintype = ITEM_FET,    subtype = "MAGIC_DE_START_0",},
    {filename = INPUT_DIR .. "_extract\\FET     _MAGIC_DE_END_000.fex",     maintype = ITEM_FET,    subtype = "MAGIC_DE_END_000",},
    {filename = INPUT_DIR .. "_extract\\FED     _FED_NAND_0000000.fex",         maintype = ITEM_FED,    subtype = "FED_NAND_0000000",},
    {filename = INPUT_DIR .. "_extract\\12345678_1234567890cardtl.fex",        maintype = "12345678",  subtype = "1234567890cardtl",},
    {filename = INPUT_DIR .. "_extract\\12345678_1234567890script.fex",      maintype = "12345678",  subtype = "1234567890script",},
    {filename = INPUT_DIR .. "_extract\\12345678_1234567890boot_0.fex",      maintype = "12345678",  subtype = "1234567890boot_0",},
    {filename = INPUT_DIR .. "_extract\\12345678_1234567890boot_1.fex",      maintype = "12345678",  subtype = "1234567890boot_1",},
    {filename = INPUT_DIR .. "_extract\\12345678_1234567890___mbr.fex",          maintype = "12345678",  subtype = "1234567890___mbr",},
    {filename = INPUT_DIR .. "_extract\\12345678_1234567890dlinfo.fex",          maintype = "12345678",  subtype = "1234567890dlinfo",},

;//-->¾µÏñÅäÖÃÐÅÏ¢
[IMAGE_CFG]
version = 0x100234;     -->ImageµÄ°æ±¾
pid = 0x00001234;       -->²úÆ·ID
vid = 0x00008743;       -->¹©Ó¦ÉÌID
hardwareid = 0x100;     -->Ó²¼þID bootrom
firmwareid = 0x100;     -->¹Ì¼þID bootrom
bootromconfig = "bootrom_071203_00001234.cfg"
rootfsconfig = "rootfs.cfg"
imagename = "output.img"
filelist = FILELIST

[sabercatpuck]

Just made a new image for the 702C

I put together a new image for the 702C (hopefully will get it tested soon) using the images I pulled from nephews tablet. This is the contents of the _extract directory afterward and a comparason of the different sizes of the tablet's raw images versus the simg's that came from the factory image.

root  32,768KB boot  8,588KB
system  524,288KB system  246,711Kb
recovery 32,768KB recovery 8,918 Kb
Note the original are sparse images and the ones pulled from the tablet are just images.  They do work, but are much bigger.
c:\A10Kitchen\packer_ics\_extract>dir
Directory of c:\A10Kitchen\packer_ics\_extract
06/15/2012  10:47 AM    <DIR>          .
06/15/2012  10:47 AM    <DIR>          ..
06/15/2012  10:47 AM            19,456 12345678_1234567890boot_0.fex
06/15/2012  10:47 AM             1,024 12345678_1234567890boot_0.hdr
06/15/2012  10:47 AM           131,072 12345678_1234567890boot_1.fex
06/15/2012  10:47 AM             1,024 12345678_1234567890boot_1.hdr
06/15/2012  10:47 AM            81,920 12345678_1234567890cardtl.fex
06/15/2012  10:47 AM             1,024 12345678_1234567890cardtl.hdr
06/15/2012  10:47 AM             1,340 12345678_1234567890dlinfo.fex
06/15/2012  10:47 AM             1,024 12345678_1234567890dlinfo.hdr
06/15/2012  10:47 AM             2,014 12345678_1234567890script.fex
06/15/2012  10:47 AM             1,024 12345678_1234567890script.hdr
06/15/2012  10:47 AM             4,096 12345678_1234567890___mbr.fex
06/15/2012  10:47 AM             1,024 12345678_1234567890___mbr.hdr
06/15/2012  10:45 AM               190 base.hdr
06/15/2012  10:47 AM            24,576 BOOT    _BOOT0_0000000000.fex
06/15/2012  10:47 AM             1,024 BOOT    _BOOT0_0000000000.hdr
06/15/2012  10:47 AM           221,184 BOOT    _BOOT1_0000000000.fex
06/15/2012  10:47 AM             1,024 BOOT    _BOOT1_0000000000.hdr
06/15/2012  10:45 AM               512 COMMON  _SPLIT_0000000000.fex
06/15/2012  10:45 AM             1,024 COMMON  _SPLIT_0000000000.hdr
06/15/2012  10:45 AM             5,741 COMMON  _SYS_CONFIG000000.fex
06/15/2012  10:45 AM             1,024 COMMON  _SYS_CONFIG000000.hdr
06/15/2012  10:45 AM            36,028 COMMON  _SYS_CONFIG100000.fex
06/15/2012  10:45 AM             1,024 COMMON  _SYS_CONFIG100000.hdr
06/15/2012  10:47 AM            26,352 FED     _CARD_FED_0000000.fex
06/15/2012  10:47 AM             1,024 FED     _CARD_FED_0000000.hdr
06/15/2012  10:47 AM           116,080 FED     _FED_NAND_0000000.fex
06/15/2012  10:47 AM             1,024 FED     _FED_NAND_0000000.hdr
06/15/2012  10:47 AM            80,960 FES     _FES_000000000000.fex
06/15/2012  10:47 AM             1,024 FES     _FES_000000000000.hdr
06/15/2012  10:47 AM               768 FES     _FES_1-1000000000.fex
06/15/2012  10:47 AM             1,024 FES     _FES_1-1000000000.hdr
06/15/2012  10:47 AM             2,368 FES     _FES_1-2000000000.fex
06/15/2012  10:47 AM             1,024 FES     _FES_1-2000000000.hdr
06/15/2012  10:47 AM             1,488 FES     _FES_200000000000.fex
06/15/2012  10:47 AM             1,024 FES     _FES_200000000000.hdr
06/15/2012  10:47 AM            18,928 FET     _CARD_HW_SCAN_000.fex
06/15/2012  10:47 AM             1,024 FET     _CARD_HW_SCAN_000.hdr
06/15/2012  10:47 AM            19,936 FET     _CARD_UPDATE_BOT0.fex
06/15/2012  10:47 AM             1,024 FET     _CARD_UPDATE_BOT0.hdr
06/15/2012  10:47 AM            20,048 FET     _CARD_UPDATE_BOT1.fex
06/15/2012  10:47 AM             1,024 FET     _CARD_UPDATE_BOT1.hdr
06/15/2012  10:47 AM             4,528 FET     _FET_RESTORE_0000.fex
06/15/2012  10:47 AM             1,024 FET     _FET_RESTORE_0000.hdr
06/15/2012  10:47 AM           112,512 FET     _HW_SCAN_00000000.fex
06/15/2012  10:47 AM             1,024 FET     _HW_SCAN_00000000.hdr
06/15/2012  10:47 AM               128 FET     _MAGIC_CRC_EN_000.fex
06/15/2012  10:47 AM             1,024 FET     _MAGIC_CRC_EN_000.hdr
06/15/2012  10:47 AM               128 FET     _MAGIC_CRC_START_.fex
06/15/2012  10:47 AM             1,024 FET     _MAGIC_CRC_START_.hdr
06/15/2012  10:47 AM               128 FET     _MAGIC_DE_END_000.fex
06/15/2012  10:47 AM             1,024 FET     _MAGIC_DE_END_000.hdr
06/15/2012  10:47 AM               128 FET     _MAGIC_DE_START_0.fex
06/15/2012  10:47 AM             1,024 FET     _MAGIC_DE_START_0.hdr
06/15/2012  10:47 AM           103,120 FET     _UPDATE_BOOT0_000.fex
06/15/2012  10:47 AM             1,024 FET     _UPDATE_BOOT0_000.hdr
06/15/2012  10:47 AM           107,936 FET     _UPDATE_BOOT1_000.fex
06/15/2012  10:47 AM             1,024 FET     _UPDATE_BOOT1_000.hdr
06/15/2012  10:47 AM             2,280 Filelist.txt
06/15/2012  10:47 AM           166,912 PXTOOLS _xxxxxxxxxxxxxxxx.fex
06/15/2012  10:47 AM             1,024 PXTOOLS _xxxxxxxxxxxxxxxx.hdr
06/15/2012  10:45 AM         5,999,616 RFSFAT16_BOOTLOADER_00000.fex
06/15/2012  10:45 AM             1,024 RFSFAT16_BOOTLOADER_00000.hdr
06/15/2012  10:45 AM         8,794,112 RFSFAT16_BOOT_00000000000.fex
06/15/2012  10:45 AM             1,024 RFSFAT16_BOOT_00000000000.hdr
06/15/2012  10:47 AM                 8 RFSFAT16_DISKFS_000000000.fex
06/15/2012  10:47 AM             1,024 RFSFAT16_DISKFS_000000000.hdr
06/15/2012  10:45 AM           131,072 RFSFAT16_ENVIROMENT_00000.fex
06/15/2012  10:45 AM             1,024 RFSFAT16_ENVIROMENT_00000.hdr
06/15/2012  10:47 AM         9,132,032 RFSFAT16_RECOVERY_0000000.fex
06/15/2012  10:47 AM             1,024 RFSFAT16_RECOVERY_0000000.hdr
06/15/2012  10:47 AM       252,631,324 RFSFAT16_SYSTEM_000000000.fex
06/15/2012  10:45 AM             1,024 RFSFAT16_SYSTEM_000000000.hdr
06/15/2012  10:47 AM                 4 RFSFAT16_VBOOTLOADER_0000.fex
06/15/2012  10:47 AM             1,024 RFSFAT16_VBOOTLOADER_0000.hdr
06/15/2012  10:47 AM                 4 RFSFAT16_VBOOT_0000000000.fex
06/15/2012  10:47 AM             1,024 RFSFAT16_VBOOT_0000000000.hdr
06/15/2012  10:47 AM                 4 RFSFAT16_VENVIROMENT_0000.fex
06/15/2012  10:47 AM             1,024 RFSFAT16_VENVIROMENT_0000.hdr
06/15/2012  10:47 AM                 4 RFSFAT16_VRECOVERYFS_0000.fex
06/15/2012  10:47 AM             1,024 RFSFAT16_VRECOVERYFS_0000.hdr
06/15/2012  10:47 AM                 4 RFSFAT16_VSYSTEMFS_000000.fex
06/15/2012  10:47 AM             1,024 RFSFAT16_VSYSTEMFS_000000.hdr
              82 File(s)    278,042,001 bytes

[sabercatpuck]

Did a comparison

So first I want to note that the resulting image (an original PMID702C image) that was created with this did successfully flash. I did a line by line comparison of the pick list above matching up the files in the _input, _output, and _extract folders to see if everything going in came out. The answer is it didn't. These files matched up with items that were in the _extract folder after I ran the extract_image.bat.

_extract\\COMMON  _SYS_CONFIG000000.fex
 COMMON  _SYS_CONFIG000000.fex
_extract\\COMMON  _SYS_CONFIG100000.fex
 COMMON  _SYS_CONFIG100000.fex
_extract\\COMMON  _SPLIT_0000000000.fex
 COMMON  _SPLIT_0000000000.fex
_output\\bootfs.fex
 RFSFAT16_BOOTLOADER_00000.fex
_extract\\RFSFAT16_ENVIROMENT_00000.fex
 RFSFAT16_ENVIROMENT_00000.fex
_input\\root.fex
 RFSFAT16_BOOT_00000000000.fex
_input\\system.fex
 RFSFAT16_SYSTEM_000000000.fex
_input\\recovery.fex
 RFSFAT16_RECOVERY_0000000.fex
_output\\vboot.fex
 RFSFAT16_VBOOTLOADER_0000.fex
_extract\\RFSFAT16_VENVIROMENT_0000.fex
 RFSFAT16_VENVIROMENT_0000.fex
_output\\vroot.fex
 RFSFAT16_VBOOT_0000000000.fex
_output\\vsystem.fex
 RFSFAT16_VSYSTEMFS_000000.fex
_output\\vrecovery.fex
 RFSFAT16_VRECOVERYFS_0000.fex
_extract\\BOOT    _BOOT0_0000000000.fex
 BOOT    _BOOT0_0000000000.fex
_extract\\BOOT    _BOOT1_0000000000.fex
 BOOT    _BOOT1_0000000000.fex
_extract\\PXTOOLS _xxxxxxxxxxxxxxxx.fex
 PXTOOLS _xxxxxxxxxxxxxxxx.fex
_extract\\FES     _FES_1-1000000000.fex
 FES     _FES_1-1000000000.fex
_extract\\FES     _FES_1-2000000000.fex
 FES     _FES_1-2000000000.fex
_extract\\FES     _FES_200000000000.fex
 FES     _FES_200000000000.fex
_extract\\FES     _FES_000000000000.fex
 FES     _FES_000000000000.fex
_extract\\FET     _HW_SCAN_00000000.fex
 FET     _HW_SCAN_00000000.fex
_extract\\FET     _UPDATE_BOOT0_000.fex
 FET     _UPDATE_BOOT0_000.fex
_extract\\FET     _UPDATE_BOOT1_000.fex
 FET     _UPDATE_BOOT1_000.fex
_extract\\FET     _FET_RESTORE_0000.fex
 FET     _FET_RESTORE_0000.fex
_extract\\FET     _MAGIC_CRC_START_.fex
 FET     _MAGIC_CRC_START_.fex
_extract\\FET     _MAGIC_CRC_EN_000.fex
 FET     _MAGIC_CRC_EN_000.fex
_extract\\FET     _MAGIC_DE_START_0.fex
 FET     _MAGIC_DE_START_0.fex
_extract\\FET     _MAGIC_DE_END_000.fex
 FET     _MAGIC_DE_END_000.fex
_extract\\FED     _FED_NAND_0000000.fex
 FED     _FED_NAND_0000000.fex
_extract\\12345678_1234567890cardtl.fex
 12345678_1234567890cardtl.fex
_extract\\12345678_1234567890script.fex
 12345678_1234567890script.fex
_extract\\12345678_1234567890boot_0.fex
 12345678_1234567890boot_0.fex
_extract\\12345678_1234567890boot_1.fex
 12345678_1234567890boot_1.fex
_extract\\12345678_1234567890___mbr.fex
 12345678_1234567890___mbr.fex
_extract\\12345678_1234567890dlinfo.fex
 12345678_1234567890dlinfo.fex

These files that were extracted but not in the above pick list(not counting the hdr files):

FED     _CARD_FED_0000000.fex
FET     _CARD_HW_SCAN_000.fex
FET     _CARD_UPDATE_BOT0.fex
FET     _CARD_UPDATE_BOT1.fex
Filelist.txt
RFSFAT16_BOOT_00000000000.fex
RFSFAT16_DISKFS_000000000.fex

Might need to go through and see if I can figure out where these files should have been, or if it is completely correct to omit them(it doesn't seem to hurt the flashing process). Also of note is there are a few files that are picked from the _output directory. If I remember right there are some files created early on in the create_image.bat file. They use other allwinner tools to make them. I think they contain checksums and package size info.