[Q] Does Acer Recovery Actually Back UP and Restore The ROMs? - Acer Iconia A500

Noob here. It doesn't "seem" like Acer Recovery is actually making backups of my ROMs. I'm really missing something either in terminology or execution and I'd like to understand what it is.
I don't know how to explain it other than to relate exactly what happened
I purchased one A500, but had to return it. I kept the backups taken with Acer Recovery, all Build A500_4.010.13_COM_GEN2
Got a new tab with Build Acer_A500_4.010.07_COM_GEN2
I immediately did a full backup:
Root (Iconiaroot 1.3)
Acer Recovery Installer
select "ClockworkMod Recovery rev1.3.4 by thor2002ro"
click "Install Recovery Image"
click "Yes" when asked to backup the current image!!!
Reboot into CW recovery.
Create a full backup: "backup and restore" -> "Full Backup"
The backup proceeded normally.
Rather than re-installing everything, I restored one of the backups from the old tab with Build A500_4.010.13_COM_GEN2
Backup installed fine, but instead of Build A500_4.010.13_COM_GEN2, I had Acer_A500_4.010.07_COM_GEN2, the same as the new tab.
I thought that was odd and I still don't know why it happened, but as I had just made a fresh new backup, I let the new tab go through the OTA updates to Build A500_4.010.13_COM_GEN2
Got everything working OK and decided to restore my new stock backup and make fresh incrementals of all the OTA updates.
Restored the original backup and now my original backup shows Build A500_4.010.13_COM_GEN2 instead of the original Build Acer_A500_4.010.07_COM_GEN2.
From these two instances, it doesn't "seem" like Acer Recovery is actually backing up or restoring the original ROM.
What is it that I'm either missing or don't understand about this process?
Thanks

If I understand the process, Acer Recovery will make backups of your recovery image. CWM does a full backup of ROM/kernel.
So, I'm not sure if I understand where you are restoring from.
If you restore through the Acer Recovery Installer, you should be just getting the old recovery image.
If you restore through the CWM menus after botting into recovery, then you are doing a full restore.

First.. it's not Acer recovery installer that's giving you the issue. The backup and restore are functions of clockworkmod.
The problem was that your flexrom did not get restored due to a bug that I demonstrated on thor's clockworkmod thread.
When doing a restore that restores data.img, it will also attempt to restore .android_secure.img and will fail, skipping flexrom which is supposed to follow. I bet you don't ever see the "Restore Successful" message after a full restore.
You need to either delete .android_secure.img from your backup set or restore flexrom separately.
Sent from my A500 using Tapatalk

PS. Clockworkmod does not backup anything from /data/media
Sent from my A500 using Tapatalk

So how to do a full backup of the image and restore if not from cwm.

Euclid's Brother said:
You need to either delete .android_secure.img from your backup set or restore flexrom separately.
Click to expand...
Click to collapse
Thanks Euclid,
Sorry about the confusion in the thread title. I thought Acer Recovery Installer had several functions: backup and restore recovery images and load CWM recovery to do the actual backup and recovery. Since I thought it did both, I assumed it was O.K. to use Acer Recovery Installer generically.
I did another restore to check what was done:
Fixing a500 Boot/recovery Checksums...
Running itsmagic
Done
Checking MD5 sums...
Erasing boot before restore
Restoring Boot Image
Restoring System
Restoring Data
Done
Screen refreshed to "Reboot Now".
As you said no "Restore Complete" message.
I wonder how many people including myself, assumed that the restore had completed successfully when they got the "done" message?
Both fixes worked well. I hope this helps someone else.
Below is the text from within CWM Recovery when .android_secure.img was deleted from the backup folder and a restore was run:
Fixing a500 Boot/recovery Checksums...
Running itsmagic
Done!
Checking MD5 sums...
Erasing boot before restore
Restoring Boot Image
Restoring System
Restoring Data
.android_secure.img not found, Skipping restore of /sdcard/.android_secure.
Restoring cache
Restoring flextrom
Restore Complete!
Restored my original stock ROM. So nice of it to ask me to update to a newer version immediately after the restore!
I did have one problem. I tried deleting .android_secure.img while rooted, using ES File Explorer with the Root Explorer and Mount File System options selected. I could never see the file on my external SD in the clockworkmod/backup
folder, so I pulled the card and manuall deleted it from my PC. I'm curios as to why this happened, but it didn't affect the result.
It was just as easy using backup and restore/advanced restore/your restore folder/ - Restore flexrom from within CWM Recovery.
I've read hundreds of post, in I don't know how many threads, sticky's included and never saw the advice about deleting .android_secure.img, manually restoring flexrom or even checking to make sure that you got "Restore Complete" I wish these things were part of an updated guide.
Lesson learned,
Thanks again

Just wondering, is there anyone working on a new recovery which will complete backups and restores without additional deletions, etc.?

bug was in thors post
The bug was mentioned.but I don't think there was much discussion about it.I don't think Thor acknowledged or tried ti fix.
With that said I could be incorrect. I however even with the bug think its a awesome tool.don't. Consider this as complaint.
Its like on page 3 or 4of the Thor recovery thread if im not mistaken
The blonde chic erica Renee

Yeah we need something reliable when restoring from backup. I tried once, cwm sees it but can't do the restore so I gave up even though I had all my apps backed up so did all one by one.
Sent from my SPH-D700 using XDA App

Related

Cannot restore from nandroid

Im running fresh 0.5.3 and have the latest amon recovery, i can do a ext+nandroid backup fine but when i try to restore after i reboot, it gets hung on the
htc screen and will not load. Ive tried several backups and it will not work when restoring. Any ideas?
Make sure you're wiping the data, cache and dalvic before restoring the backup.
Are you sure the backup is getting created?
I know SteelH was posting yesterday about the NAND + EXT backup not even working with amon recovery.
I personally don't even know what it does, but all my backups are just "NAND backups and seem to work fine.
I'm assuming you used Amon_ra to create the backup and you're using Amon_ra to restore?
I created a backup with amon_ra and tried to restore with Clockworkmod and the backup doesn't even show up and vice versa. I found out by trial and error that backups created by clockworkmod have to be restore with clockworkmod and backups created by amon_ra have to be restored with amon_ra.
I don't know if that's the case for everyone, but it sure is for me. I'm running whitslack's 1.47 and Evolution V9.
Back to the Nand+Ext, maybe SteelH has figured it out, maybe send him a pm or search for his posts in the Q&A forum from yesterday.
make sure your batt has enough power
I am fully charged when i nandroid. It creates the backup and restores it but when i reboot it freezes on the htc screen. So this is a bug with the amon recovery image then? It would be nice to be able to backup & restore my ext apps because i use apps2sd. I could use titanium backup but nandroid is faster.

Can't restore backup on Nexus 7

Hey all, I updated to a beta of Paranoid Android that screwed up everything. I created a backup ( and actually have several more older ones) with ClockworkMod Recovery. The very latest backup will not restore for whatever reason, but the main issue is that it's the only backup I can even see.
All the other backup folders don't even show up in recovery. Accessing /sdcard/ I can see them all. Any ideas on how to restore?
Actually, the one backup that CWM Recovery shows, I can't see under /sdcard/clockworkmod/backup/
I'm guessing CWM Recovery is pointed in the wrong directory..?

TWRP 2.6.0 restore data

Ladies and gentlemen,
Recently, whilst flashing a new ROM, I had an issue. I tried to restore a backup that I created with TWRP 2.6.0 with the same version. I got to the "Restore data" stage in the logs, and it failed.
I have two data.ext4 files in my TWRP backup folder: the first is data.ext4.win000 and data.ext4.win001. I'm thinking this is the issue.
I have already flashed a ROM and booted, so I am out of the woods. Just wanted to know if anyone has had any success with split data files in a TWRP recovery.
Thanks for your time.
richardpunch said:
Ladies and gentlemen,
Recently, whilst flashing a new ROM, I had an issue. I tried to restore a backup that I created with TWRP 2.6.0 with the same version. I got to the "Restore data" stage in the logs, and it failed.
I have two data.ext4 files in my TWRP backup folder: the first is data.ext4.win000 and data.ext4.win001. I'm thinking this is the issue.
I have already flashed a ROM and booted, so I am out of the woods. Just wanted to know if anyone has had any success with split data files in a TWRP recovery.
Thanks for your time.
Click to expand...
Click to collapse
Look for TWRP-Recovery-jfltespr-2.5.0.2 seems to be the most reliable for backup and restores right now.
The 'splitting of the EXT/data is NOT the problem. That's the way twrp is compressing the images.
Also there are some ROMs that have partition problems with certain kernels, so take note of that.
I make a crap load of nandroids and switch back and forth pretty often. 2.5.0.2 has been the most reliable for me.
Once more thing I do is verify the nadroid via the AFV app. I boot to recovery, create backup (always of every partition) then boot to ROM and run the AFV app on the backup and make sure it verifies. Then I'll boot back to recovery and wipe/format and flash away according to the dev's instructions.
Leader,
Thanks for such an informative write up. I will check into rolling back to a different twrp build. It's an unpleasant solution, but if it works I'll have to bite the bullet.
Thanks again!
-Mobile post

Failed TWRP restore

So I decided to try and flash Ubuntu last night... I booted into recovery made a backup 15min and 2.5 GB later it was done... wiped flashed no go would not boot... so back to recovery I choose my restore file... system says it was successful but when restoring the data it fails... I'm on twrp 2.5 ...then I tried to just restore the system when booting up I get that static image you see on cm flash every 5 sec but never boot nor goes inyo the boot animation...is there anyway to use this restore file... I just need the data part.. I have messages that i need to show my lawyer and numbers that I need... TiB won't restore my messages either....
Sent from my XT907 using xda app-developers app
You will need TWRP 2.6.3 / PhilZ / or a newer CWM that supports adb in recovery (not sure is 2.5 does)
First off, all of your pictures and other stuff are stored at "/data/media" or "/data/media/0" and are not "wiped" unless picked. These are both accessible in recovery, and you could do an "adb pull ....." to get those files to a PC. At this point you should have your pictures.
Sounds like Ubuntu messed some things up, and when you restored "/system" only it won't boot because of missing data. I once had a problem like this bouncing back and forth between 4.3 and 4.2. Assuming you were on a custom ROM, maybe try wiping completely including "/data/media" DO NOT WIPE "/DATA/MEDIA" IF YOU HAVEN"T BEEN ABLE TO PULL THE FILES VIA ADB IN RECOVERY!!! YOUR PHOTOS WILL BE GONE!!! Sorry for the bold caps, I just didn't want you to miss it. Next install your custom ROM, boot, and do enough setup to get to the home screen. Now go back to recovery and your backup should restore. From here you could "adb push ..." your files back.
Updating TWRP is one way to solve this in the future, like JB already posted. However, to remedy on 2.5, do a clean wipe prior to restore, mounting system prior. Then, restore only the boot.img from the ROM you want and then restore the full ROM you want. This is how I was able resolve this same issue. Hopefully, it will work for you.
I was on stock deodexed debloated prior to all this... after a few tries at the restore I just flashed that same ROM and used TiB to restore what I had on last back up... tonight I'll try and restore that twrp backup ... but either way I guess I'll be updating my recovery... I'm not worried about all my pics n what not I keep all that on the external SD card now...
Sent from my XT907 using xda app-developers app

TWRP sayd system not mounted, then rebooted during restore, phone is softbricked

I was bootloader unlocked, latest TWRP installed, systemless root with SuperSU 2.6, cataclysm rom, ex kernel, layers, xposed. I had made a ton of backups and even kept some of them backed up in another locations. I needed to restore a backup in TWRP. At first it wouldn't let me, kept saying that phone system was mounted as read only.
this is my question #1 - How do you mount system for read in TWRP? I see there's an option called "mount," I go in there, i see settings I can select, but I don't see any option to "execute" or "apply" settings (like TWRP has on other screens - swipe to backup, swipe to restore, etc). There's no "clicke here to mount option." what do you do here?
#2 - it finally mounted rw, i think, but after picking my latest backup, it started and then when it got to 19% it reboot the phone. Phone is softbricked.
#3 - I'm very confused about all the checkboxes to restore, and all the checkboxes to wipe.
What should I be wiping and what should I be restoring? When making backups I checked all the boxes.
I had the galaxy nexus before and I knew that phone and clockworck mod inside out. TWRP is confusing and glitchy to me. I'm stuck and work with a phone without an OS and I'm starting to freak out, and don't have A to C cables with me.
Please explain where I went wrong here and how to do things correctly. I want to understand what I'm doing better, not just follow steps.
When you restored, with all the check boxes did you click "system image" for restore?
You should wipe then restore only system, data, and boot.
dontbeweakvato said:
When you restored, with all the check boxes did you click "system image" for restore?
You should wipe then restore only system, data, and boot.
Click to expand...
Click to collapse
Yes, I selected all the boxes, including system image I believe.
I did a wipe. I selected all the boxes. Went back into TWRP and now all my backups are gone. I said reboot, and TWRP said there's no OS installed. I think I deleted everything. I should not have wiped. I do have a backup saved on a computer, it's a folder with lots of .img files inside. How can I get that onto my phone with only having fastboot and TWRP modes available? I mean how can I place it on the phone in a way that TWRP would recognize it and restore from it.
I ended up just flashing the stock google image and that at least gave me a working phone back.
Yes. You beat me to it, that's what I was going to say. You have to reflash. Just remember for future references you only need to backup boot, system, and data( and efs etc). But Not "system image" that'll Bork your stuff up.
dontbeweakvato said:
Yes. You beat me to it, that's what I was going to say. You have to reflash. Just remember for future references you only need to backup boot, system, and data( and efs etc). But Not "system image" that'll Bork your stuff up.
Click to expand...
Click to collapse
I'd like to really understand this better. Do you know why system image borks the phone? Also, when you say efs etc., do you mean "absolutely everything except system image"? (I actually didn't see EFS listed there)
Well boot system and data. But you also need efs cause thats your imei. So just look around and familiarize with what youve found so far. Right now Im trying to flash 6.0.1 with a systemless root. Its kinda goin ridiculous right now because there aren't any directions or suggestions.
If you get to "no OS installed" restoring system image, then system will get you back
Sent from my Nexus 6P using Tapatalk
zgroten said:
If you get to "no OS installed" restoring system image, then system will get you back
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
After it said no OS installed, I tried to restore system image from my TWRP backup, and the restore failed and the phone reboot itself at 19% restored. I had to ADB flash the factory system image from google. This brings me back to the original question.
Why was the restore in TWRP failing?
Did you mount system in TWRP before attempting to restore?
Sent from my Nexus 6P using Tapatalk
mistermojorizin said:
After it said no OS installed, I tried to restore system image from my TWRP backup, and the restore failed and the phone reboot itself at 19% restored. I had to ADB flash the factory system image from google. This brings me back to the original question.
Why was the restore in TWRP failing?
Click to expand...
Click to collapse
actually in twrp you could of wiped, then restored boot, system , data and it would of restored everything

Categories

Resources