I'm going to try flashing it twice.
I think what is happening is because it is a maxvar image in that the root is lzma compressed to make the writable /var partition larger.
If this is the case then the /var will not be readable on 1st boot.
If there is no /var then it creates it a /var and copies all the contents of /var_init to /var which is why none of zas786 changes are still there.
After the 2nd boot the rewritten /var is still there so the files from the jffs part of the backup is written to /var and not the /var/init.
I suppose this would mean the same happens if you go back to a non lzma compressed root image ?
in the time it took me to write this it has finished and all is working as it should be so some of us will need to flash it twice.
Thanks All
I think what is happening is because it is a maxvar image in that the root is lzma compressed to make the writable /var partition larger.
If this is the case then the /var will not be readable on 1st boot.
If there is no /var then it creates it a /var and copies all the contents of /var_init to /var which is why none of zas786 changes are still there.
After the 2nd boot the rewritten /var is still there so the files from the jffs part of the backup is written to /var and not the /var/init.
I suppose this would mean the same happens if you go back to a non lzma compressed root image ?
in the time it took me to write this it has finished and all is working as it should be so some of us will need to flash it twice.
Thanks All
Last edited: