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;
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.