Originally Posted by marvin02

My question is will that recovery.img, extracted from the zip, work with fastboot? This would be used if there is a problem with the Venue (mine is still under warranty).

There is no .pkg file for the 307 ROM that I am aware of.

I see, sorry I misunderstood the question. I have flashed the .img files for 307 from the zip file via fastboot before and it worked fine.

The recs in the stock image thread are the actual recoveries for that rom.

Those were all dumped manually, this is the first of any custom recovery that i've made available, publicly or privately

I have installed this and am playing with it.

I can say that not even a battery pull will stop the factory reset from the first screen if you choose it by accident and there is no prompt to continue. You can probably figure out how I know this.

I did get this error:

E: unknown volume for path [/sd-ext]

When selecting to wipe dalvik cache.

And when viewing the log I got a bunch of lines that said:

failed to open /sys/class/android_usb/android0/state: No such file or directory

I did a wipe data/factory reset from the first CWM screen. My Venue booted fine afterwards. The output is attached below.

Tested with no apparent ill effects:

first CWM screen:

wipe data/factory reset
wipe cache partition

advanced screen:

wipe Dalvik cache (see error note above)
wipe battery stats
Key Test
Show Log
Fix permissions (takes a bit, be patient)

Reboot recovery just does a normal reboot unless you hold both volume buttons.

Doing a factory reset from the first screen did not remove CWM and did not remove root.

Problem: Backup and restore sat on "Backing up data..." for quite a while. The first time I did a battery pull after a few minutes and tried again. The second time I let it sit for about 12 minutes and it never moved off of "Backing up data...". What should happen when it completes a nandroid? Does it take longer than this?

Originally Posted by marvin02

I did get this error:

E: unknown volume for path [/sd-ext]

When selecting to wipe dalvik cache.


Problem: Backup and restore sat on "Backing up data..." for quite a while. The first time I did a battery pull after a few minutes and tried again. The second time I let it sit for about 12 minutes and it never moved off of "Backing up data...". What should happen when it completes a nandroid? Does it take longer than this?

I get the same results across the board (except factory wipe - wasn't going there). I also get the same dalvik wipe error on my Viewsonic GTab, nothing to worry about.

Originally Posted by marvin02

I did get this error:

E: unknown volume for path [/sd-ext]

That's a known (non)issue, sd-ext is what data2ext uses as it's partition, it's also known as perfmod on the s5. As the venue has no data2ext/perfmod it's not relevent

Originally Posted by marvin02

And when viewing the log I got a bunch of lines that said:

failed to open /sys/class/android_usb/android0/state: No such file or directory

that files does not exist in the venue's kernel, /dev /proc and /sys are generated at bootup by the kernel, the contents are determined by what's turned on/off in the kernel. /sys/class/android_usb simply does not exist in the kernel (I used the 408 recovery kernal btw)

The most I can do is try and surpress it, but that's only debug lines in the log, usb mounting works for me so it's not critical

Originally Posted by marvin02

Doing a factory reset from the first screen did not remove CWM and did not remove root.

Root always copies over /system/(x)bin/su and that cant be removed by a fac reset.

Fac reset only wipes /cache and /data

Unlike streakmod on the s5 though, you should be able to trust the fac reset in CWM5.5

Originally Posted by marvin02

Problem: Backup and restore sat on "Backing up data..." for quite a while. The first time I did a battery pull after a few minutes and tried again. The second time I let it sit for about 12 minutes and it never moved off of "Backing up data...". What should happen when it completes a nandroid? Does it take longer than this?

It's always safe to pull the batt during nandroid READS but never writes. What is the exact step it stops at? I've had some issue with nandroids in the unreleased 5.0.2.7 but I thought it was fixed in 5.5.0.x.

If there are any nandroid issues it's likely in CWM itself as I havnt modified CWM at all while compiling any of the CWMs


The nandroids are not perfect yet regardless, I'd recommend rooting and using titanium backup (or whatever you prefer) on top of nandroids till there's more reports of success/issues

Originally Posted by TheManii

. . .What is the exact step it stops at? I've had some issue with nandroids in the unreleased 5.0.2.7 but I thought it was fixed in 5.5.0.x. . . .

See the attached image. It gets to "Backing up data..." and then just sits there and never completes.

Edit: the image is from the first attempt. It stopped at the same spot on two other attempts.

Does it start backing up at all or immediately stops right as it hits data?

if it's the 'lost+found' bug it should stop after hitting it hits the 'lost+found' folder and have some of the contents of data

Originally Posted by TheManii

Does it start backing up at all or immediately stops right as it hits data?

if it's the 'lost+found' bug it should stop after hitting it hits the 'lost+found' folder and have some of the contents of data

We probably cross posted, I added an image of exactly where it stuck.

It might an issue in CWM 5.5 then

S5:
cannot back up userdata partition (/firstboot)
can back up innerSD data partition (/data)

v:
cannot back up userdata partition (/data)

They're both the partitions on the nand itself, the s5 one just happens to be smaller.

For the same reason I'm not yet releasing CWM 5.5 for the s5, a fac reset might fix it so you can make nandroids afterwards (if you restore with TB afterwards it may still continue working). It SEEMS to work for me but that would mostly defeat the purpose of nandroids.

Originally Posted by TheManii

. . . a fac reset might fix it so you can make nandroids afterwards (if you restore with TB afterwards it may still continue working). . . .

Those first tests were immediately after a factory reset. I am sure you are aware of the work on StreakMod Recovery and might want to see what was done to fix nandroids on that. That is the one feature of CWM I would like to see as solid.