I have followed the steps in the quick start guide:
bootm2recovery.sh to restart in recovery mode => no fails but I suspect It’s booting in normal way. In fact I can still login the system again by ssh (serial port doesnt exist, so no posibility to enter by this way…)
Killall dsupdateimg => the process doesn’t exists
mount /dev/mmcblk2p8 /f => device to mount doesn’t exists (mmcblk2p8). The nearest named device found in dev is mmcblk0p7…and it’s already mounted (at / )
dd if=/dev/mmcblk2p7 of=/f/rootfs.img bs=10M => no mmcblk2p7 nor mmcblk2p8 so I haven’t tried this and next steps …
Yeah, I’m currently trying to do the same but so far no luck. I’ve managed to backup the file system as a whole, but then you have to use the sdk to create a new bootable image and that has to be performed on an ubuntu vm etc etc… So I have to read the documentation (if i can find it) and try it that way… Let me know if you have any luck
How did you manage to backup the filesystem? is bootm2recovery.sh restarting in recovery mode in your device? can you mount /dev/mmcblk2p8? Did you need to connect by seral port? Wich steps did you follow?
In the other hand I think the img you are backing up is just the rootfs, which, I suspect, could be flashed alone, as is, with RKDevTool (Download Image tab). I think SDK is only needed if you plan to make a complete image with rootfs, bootloader, recovery part…