Option 2 worked for me, thanks ZeroNull !

Hi Folks,
I've had the same problem as moom999, Option 2 did the trick, but I've had to change a bit the procedure, because mount -a in adb shell raised an error
Then in CWM I used the mounts and storage menu to mount /system, this being done, I've been able to run those commands :

adb shell "cd /system/etc && mv install-recovery.sh install-recovery.old"
adb reboot

I hope this may be useful to some people

Just a note;

On my tab, the process completed, but still said in fastboot mode.

Also, acer logo was showing. But CMD window said recovery installed.

Just shut down, unplug USB, and reboot back to recovery (Vol- and PWR).

Note to previous 500/501 users, you have to be very quick to release the PWR button when it vibrates. It's not like the 500/501 when you waited for text to appear, because there wont be any till you release and recovery boots.

At this point, I highly suggest you do a system backup.

MD

Urgent

---

Ok. Seems a bug in the recovery.

Restoring from previous backup, first takes a very long time.

Restore finishes.

Tab boots.

Downloaded widget was missing from home screen. Wallpaper changed to default.

Most of any downloaded apps will not function (receive error). All user data lost resulting in resetting most log-ins.

Cannot download apps from the Market anymore. Market works just cannot download.

Tablet will not shut down (5+ minutes at the shut down screen).

Original recovery backup will not install. Stops at restoring Data, then just stays there.

In the Wipes menu of CWM, cannot wipe User Data. Just stays at formatting /data.

So it appears the Data functions in CWM do not work.

MD

In other words, the current CWM is just not working properly, resulting in corrupt data system and cache partitions.

Remember, development on the 70x is new. And these things will happen to those that aren't afraid to brick their tablets. This is how things get fixed.

So for now, till things are worked out, I would advise to hold off installing the current CWM, until the bugs get worked out.

MD

This was an irresponsible post given the CWR was not thoroughly tested. It simply doesn't work to flash a ROM or Backup and Restore.

---------- Post added at 07:58 AM ---------- Previous post was at 07:41 AM ----------

Originally Posted by ZeroNull

I think the problem in version bootloader, which is installed on your tablet.
This problem can be solved in two ways:
Option 1. Change to another the firmware version, in which works command bootloader - "fastboot boot recovery.img"
Option 2. After running the installation script CWM recovery, when comes to message:

turn off the tablet. And then perform the following steps:
1. Press and hold down the 'Volume -'. Power on the tablet. After starting the CWM recovery - releasing button 'Volume -'.
2. Open the directory with the unpacked archive. Launch from this directory the Windows command prompt. And enter the following commands:

adb shell "mount -a && cd /system/etc && mv install-recovery.sh install-recovery.old"
adb reboot

Now CWM recovery will not be overwritten with the original recovery.

PS: Google Translate forever.

How would I get the original recovery back in place - CWR is not working on this device to flash ROMs and I'm currently inoperable.

Originally Posted by boomerod

This was an irresponsible post given the CWR was not thoroughly tested. It simply doesn't work to flash a ROM or Backup and Restore.

---------- Post added at 07:58 AM ---------- Previous post was at 07:41 AM ----------



How would I get the original recovery back in place - CWR is not working on this device to flash ROMs and I'm currently inoperable.

Personally, if your tab is still running, I would not mess with it yet. If it's not running, (hangs at acer screen) then the only thing I can advise, is to try turning it in to the service center. They might charge you, but it's always a risk.

Right now, the devs involved are without tabs, so until they get fixed, not a lot will be able to be done. It might be weeks or months till some brave souls try getting recovery working correctly.

My theory, is that if you rename install-recovery.old back to install-recovery.sh (switch the positions of the adb commands), there's a possibility when you reboot, it will try to overwrite the CWM recovery that is installed, with the stock. In theory. Of course my tab is in repair as we speak so there is no possible way to test this )

At the best, it will work. But I lay 50/50 when you reboot, you will get a message "loading recovery kernel", and it just stays there. Like I said. 50/50, and I lean towards my theory.

Still doesn't negate the fact you have to try and flash a stock bootloader to take care of the unlocked one as currently there is not a known method to "re-lock" the bootloader via fastboot. Might be able to do it though adb also, as currently, I don't believe NVFlash works yet for the 70x. You might be able to flash a stripped "update.zip" which contains only the necessary commands and bootloader.blob file. But again, 50/50.

If we had an EUU (or RUU as with phones) update file, it's possible to reinstall the OS and repair the corrupted /Data partition. Possible, but only in theory. This of course would require you have your current UID number. You can check the 500 forums on how to get your UID, and folks, I highly advise you do this when you get the chance. I would probably run a fastboot command to wipe data before trying to install any type of update.zip though.

Another a700 rom if it's not already listed;
https://docs.google.com/folder/d/0B_...0k1RjhHTFRab1U

The deal is, if your tab is still running with the current CWM. Stay out of there and don't flash anything that might cause a bootloop. And don't go deleting system apps, as the wrong one could cause that also.

Believe me, nobody wanted to put out anything that could brick a device. But this is what happens sometimes, especially when people might be a little too anxious to root and such. And when we all took that first step, and unlocked the bootloader, we committed ourselves to whatever happened. Good or bad. We all know the risk, especially when a device was only released for a few days.

Heck, I'm not angry at any of the Devs involved in these CWM's (510/700). At least they don't sit on their butts and do nothing, and are willing to do things for the users. This time, it just didn't work. That's all. And Zero-Null has done a lot of good.

MD

Amen to that Moscow Desire !

I personally have been lucky as my A701 still runs fine rooted and with CMW... I won't touch anything for now. I just hope we'll see an nvflash tool and the needed files/parametres to go with it. That would help devs a lot and give a little more security to people flashing their devices.

Originally Posted by paugustin

Amen to that Moscow Desire !

I personally have been lucky as my A701 still runs fine rooted and with CMW... I won't touch anything for now. I just hope we'll see an nvflash tool and the needed files/parametres to go with it. That would help devs a lot and give a little more security to people flashing their devices.

Thanks Mate.

2 - 3 weeks before I'm back in the saddle again. As I've been told. Long story.

Still rockin the 501 though!!!!

MD

Rewrote the program for CWM 5.5.0.4 firmware directly on the device - much more convenient. Plus, to make a copy of the old firmware loader for the rollback.
http://depositfiles.com/files/hoi1ulkyh