[Verizon] Clockwork backups not found?

[Desertbum]

Howdy AF members! I have been loving all these ROMs and switching between them to find something I like. I have a question about my CWM backups though and I wanted to see if anyone else had the same issue. I have made a nandroid backup of every single thing I have flashed on my phone. Then I would rename the file from my computer so that I know what I was running and what issues I have. Yesterday I tried to restore a certain nandroid but the phone "could not find" it. Then the same thing happened for all of my OTHER backups. It's not really a big deal but I would like to know if maybe I just did something wrong. Any insight would be appreciated.

 

[quickaudi]

Which CWM version are you using?

 

[colchiro]

Sounds like you added spaces in the file names. Remove them or change them to underscores or hyphens.

Scary Alien's Android File Verifier can check if they're ok. Just open the app and long press on the folder name to bring up the "verify nandroid backup" dialog.

He's adding the same capability for TWRP.

 

[Desertbum]

Sounds like you added spaces in the file names. Remove them or change them to underscores or hyphens.

Scary Alien's Android File Verifier can check if they're ok. Just open the app and long press on the folder name to bring up the "verify nandroid backup" dialog.

He's adding the same capability for TWRP.

Oh shibang I had spaces in my file names... Thanks for the heads up. Now I will go scold myself in the corner haha

 

[scary alien]

Sounds like you added spaces in the file names. Remove them or change them to underscores or hyphens.

Scary Alien's Android File Verifier can check if they're ok. Just open the app and long press on the folder name to bring up the "verify nandroid backup" dialog.

He's adding the same capability for TWRP.

'Tis done!

AFV supports TWRP now .

Enjoy!

 

[colchiro]

Thanks Scary... Can it check for bad chars in file names?

 

[scary alien]

Thanks Scary... Can it check for bad chars in file names?

Actually, it's funny you mention that...

The app actually has code in it to do just that--but for Amon_RA custom recoveries Nandroid backups. Amon_RA, at least for the HTC Droid Eris, used to name the Nandroid backups as /sdcard/nandroid/<device serial number>/ccyymmdd-hhmm with the boot.img, cache.img, data.img, and system.img files in there. I recognize and match on the device's serial number to know that it's an Amon_RA Nandroid backup and then parses and audits the director name from there.

Here's my actual code:

// audit various characters that might cause a problem when Amon_RA tries to invoke nandroid-mobile.sh via shell
//
if ( ( work_selected_file.indexOf(" ") > 0 ) ||    // " " - causes rest of name to be truncated (treated like a subsequent parameter)
     ( work_selected_file.indexOf("*") > 0 ) ||    // "*" - could be expanded by the shell into list of files in current directory
     ( work_selected_file.indexOf("?") > 0 ) ||    // "?" - causes 'invalid argument'
     ( work_selected_file.indexOf(">") > 0 ) ||    // ">" - could cause redirection
     ( work_selected_file.indexOf("<") > 0 ) ||    // "<" - could cause redirection
     ( work_selected_file.indexOf("|") > 0 ) ||    // "|" - could cause data piping
     ( work_selected_file.indexOf(";") > 0 ) ||    // ";" - could cause statement termination (separation)
     ( work_selected_file.indexOf("&") > 0 )   )   // "&" - could cause process to launch in the background
{
  display_popup_message ("Warning", "Selected Nandroid backup directory path / filename contains characters that might cause a Nandroid restore to fail.\n\nSelect again to process anyway", "Okay");
  warnings_displayed++;
}

This really used to be an issue for Amon_RA custom recovery because it did the backups by invoking a shell script (nandroid-mobile.sh) and the name of the Nandroid backup was passed by name to the shell. Having wonky characters could easily make the shell script not be able to recognize the backup name.

Its not so much of an issue nowadays because the backups are created directly in C-code and not passed as shell arguments, but, as we see here, its sometimes an issue.

I'll put this on the list for the app's next release .

Cheers!