[HD2 Android NAND Development] NYLimited:
Sorry, one more note for way in the future stuff. I note that the img file is now 5.58 MB which is larger than the recent CWM partitions of 5 MB and way larger than old CWM partitions of 3 or so MB. Inevitably, a bunch of n00bs will try to install this update when you release it into a partition way too small and.. well, you know the rest. Since my recovery partition is 8 MB I don't have the problem but I know some will.

I don't know how much work (or if even possible) but if the updater_script could run a test (another script?) for recovery partition size a lot of nasty posts could be avoided down the line. :)

OK, about the new code and the tests....

When trying to set DataOnExt options the default "/data" is displayed for path. Changing this to, say "/sd-ext" is shown as "valid" but after pressing enter and exiting the screen it may or may not be saved. Re-entering the advanced screen once again will show /data as the path instead of what was specified earlier. I have a feeling this is not working since after returning to the backup screen and doing a refresh on sizes does not change anything - /data is still empty after the refresh.

This may well be more work than it is worth but have you thought of a file explorer like path selection method? :)

Can you offer any clarification on the use of MD5 on/off switch? Why would we want to turn it off?

EUREKA! Restoring the boot partition in a Magldr system seems to have worked - or, at least, it didn't wipe out the previous one! :D Took a grand 2 seconds (can you speed it up??) to restore /boot and the darned thing booted successfully afterward.​

The one thing that bothered me is the fact that when the backup was completed TWRP went back to the main menu. Since backups tend to take a while chances are I will not watch the entire process. If it is on the main menu when I return I have no quick way to know if it was successful or if something went wrong during the process. I suspect this may be the same for restoring also.

While checking the log is a nice option perhaps a simple "Backups successful /n Press enter to continue .." might be of help here. Just a thought so you don't get bored. :eek:

After doing a FULL backup which included the sd-ext (my data) partition the app stopped on a "Completed.. reboot" message. It did not do that earlier on a much smaller backup - no idea what the difference might have been...

Just curious. Why is it breaking the sd-ext backup into multiple archives? The FAT32 file limit is 4 gig. My total data in that partition is less than 2 GB. I have a suspicion that the code is looking at the

size of the partition

(which is 4 GB), not the actual data to decide whether multiple archives are needed or not.

PLEASE NOTE I have not yet done a full restore using the multiple zip files. If someone has time before I get to it please advise of outcome!

This is what the folder looks like after TWRP is done - note the multiple files for sd-ext:

And this was the original, CWM backup:

I will have to play more with compressions and MD5 stuff (which still puzzles me - why is the restore default MD5 turned off? - but this is definite progress!

Thank you!!!!