Help A yaffs2 image? WTH?

[Sokudo Ningyou]

I'm trying to backup my rooted X before I try applying the Clock Removal patch. Haven't had a problem before, but now, in D2, I'm getting almost to the end and then an error generating an md5 cheksum. Try again, and it immediately tells me it can't generate a yaffs2 image?

 

[scary alien]

I'm trying to backup my rooted X before I try applying the Clock Removal patch. Haven't had a problem before, but now, in D2, I'm getting almost to the end and then an error generating an md5 cheksum. Try again, and it immediately tells me it can't generate a yaffs2 image?

You mean you are in ClockworkMod recovery, right (not Droid 2 Bootstrapper) and are trying a to do a Nandroid backup?

Do you have enough free space on your SD card? (although by the time the nandroid.md5 file is created, you've already used/allocated all of the space you need for your Nandroid backup files).

 

[Sokudo Ningyou]

You mean you are in ClockworkMod recovery, right (not Droid 2 Bootstrapper) and are trying a to do a Nandroid backup?

Do you have enough free space on your SD card? (although by the time the nandroid.md5 file is created, you've already used/allocated all of the space you need for your Nandroid backup files).

Yeah, plenty of space. I've just never seen this before, and I can't figure out what could cause it.


I go into Droid 2, click on Reboot Recovery, then Bootstrap Recovery, then go on from there once the phone reboots.

 

[scary alien]

Yeah, plenty of space. I've just never seen this before, and I can't figure out what could cause it.


I go into Droid 2, click on Reboot Recovery, then Bootstrap Recovery, then go on from there once the phone reboots.

Lemme look at the source real quick (if you have an exact error message, that would help ).

BRB...

 

[scary alien]

Was this the format of the error message?:

"Error while making a yaffs2 image of xxxxx"

edit: and what was the value of "xxxxx"?

 

[scary alien]

Hmmm...I've looked in two different versions of ClockworkMod recovery source at the nandroid.c code. Both basically ended-up invoking the mkyaffs2image funciton (see the source here: /var/www/vhosts/netmite.com/android/mydroid/external/yaffs2/yaffs2/utils/mkyaffs2image.c).

The mkyaffs2image function will basically (from what I can tell) return a error code of 1 in just about any circumstance that can produce an error (not enough free space, write error, invalid directory, improper formatted filesystem, etc.).

I believe that ClockworkMod creates a /cache/recovery/log file containing a transcript of session and error messages that would get produced, but you'd probably have to use the Android SDK's adb utility to shell into your DX while recovery is still running to retreive the log file ("adb shell pull /cache/recovery/log cwm-recovery-log.txt" for example) to really identify the exact error or possible cause.

I supposed you could try using a different (newly formatted and empty would be best) SD card to really eliminate and isolate the possible causes.

Hope this helps.

Cheers!

 

[Sokudo Ningyou]

Hmmm...I've looked in two different versions of ClockworkMod recovery source at the nandroid.c code. Both basically ended-up invoking the mkyaffs2image funciton (see the source here: /var/www/vhosts/netmite.com/android/mydroid/external/yaffs2/yaffs2/utils/mkyaffs2image.c).

The mkyaffs2image function will basically (from what I can tell) return a error code of 1 in just about any circumstance that can produce an error (not enough free space, write error, invalid directory, improper formatted filesystem, etc.).

I believe that ClockworkMod creates a /cache/recovery/log file containing a transcript of session and error messages that would get produced, but you'd probably have to use the Android SDK's adb utility to shell into your DX while recovery is still running to retreive the log file ("adb shell pull /cache/recovery/log cwm-recovery-log.txt" for example) to really identify the exact error or possible cause.

I supposed you could try using a different (newly formatted and empty would be best) SD card to really eliminate and isolate the possible causes.

Hope this helps.

Cheers!

Mutter, mutter, figures it'd be something that would be more work than I want to bother with. Oh, well; thanks anyway! It's just never been a problem before with Droid X Bootstrapper, but maybe it's because it's Droid 2?

 

[scary alien]

Mutter, mutter, figures it'd be something that would be more work than I want to bother with. Oh, well; thanks anyway! It's just never been a problem before with Droid X Bootstrapper, but maybe it's because it's Droid 2?

Just to be clear, its actually ClockworkMod recovery (where the Nandroid backups are launched from) and not Droid 2 Bootstrapper that we're talking about here, right?

Droid2Bootstrapper is what launched the ClockworkMod custom recovery, but its the custom recovery that's actually involved in the Nandroid backups (where you'd encounter a yaff2image-related error).

If you are getting ClockworkMod to launch, then its not an issue with Droid 2- vs. Droid X- bootstrapper...(since it launched).

Just wanted to make sure we were really talking about same things here .

Cheers!

 

[Sokudo Ningyou]

Just to be clear, its actually ClockworkMod recovery (where the Nandroid backups are launched from) and not Droid 2 Bootstrapper that we're talking about here, right?

Droid2Bootstrapper is what launched the ClockworkMod custom recovery, but its the custom recovery that's actually involved in the Nandroid backups (where you'd encounter a yaff2image-related error).

If you are getting ClockworkMod to launch, then its not an issue with Droid 2- vs. Droid X- bootstrapper...(since it launched).

Just wanted to make sure we were really talking about same things here .

Cheers!

Yeah, what you said. My bad.