Thanks to you both. I have the problem with the use of "u-boot" being used when it is not used in flashing the program. i.e. if you unpack an Img.img you will get the normal group of files. which do not include a "u-boot" file. They will include a loader.bn file for bootloader, and the parameter file is a parameter file. Where I have ran into problems is the labeling of the parameter file as a "u-boot" 1G data file, when trying to load a parameter for increased internal storage or changing to a larger system file. Have been able to copy and paste new parameter file into the u-boot 1Gdata parameter file, but this can get confusing. I have one question is there actually any use what so ever for a "u-boot" and the RK3288 except for a Nand, which I doubt we will ever see used with this chip. This is my frustration is for have been working with u-boot, kernel 3.10, android, and nand on the RK3188 for months and there seems to be NO solution so far, I believe Astralix is still working on this. Has any one actually tried u-boot on the RK3288 to see if it actually (RK3288 and internal nand) works. can we possibly redo the 2.17 rktool to use "parameter" instead of "u-boot 1G data". ----cappybob |