I am trying to create a backup image, based on the stock ubuntu server image, so that all my configurations and custom settings can be easily dropped onto other CM3’s. i was able to do it in a convoluted way (mount mass storage to the device while it was running, dd the live image to a .img file on the storage device, then mount the storage device to a normal linux box, and flash the dd’d image file to another CM3 using rkdeveloptool). that method works fine, but is a little round-a-bout. I would liek to just use the rkdeveloptool to pull the image, but whenever i do, the image that is created wont boot after i write it to a CM3. to pull the image, i run the commands:
sudo rkdeveloptool db rk356x_spl_loader_ddr1056_v1.06.110.bin
sudo rkdeveloptool rl 0 9280000 image.img
the 9280000 number is coming from the partition sizes when i run fdisk on the original image while it is live, getting an end sector of 9273343, so the 9280000 should be plenty big enough (the image fiel created by dd is showing as 4.74G, the one created by rkdeveloptool is 4.75G. i write either image the same way, by running the commands
sudo rkdeveloptool db rk356x_spl_loader_ddr1056_v1.06.110.bin
sudo rkdeveloptool wl 0 image.img
but the dd’d image will boot, while the one created by rkdeveloptool will not. i do not have access to the debug console, so i cannot see what the bootloader might be saying. anyone else having this problem?