Database Users

[Q] How to create a Backup of a stock A500 ?

Hi fellow Android lovers
I'm still not sure how to make a proper backup of my completely stock A500 (HC 3.0.1).
My plan is:
1. Root with Gingerbreak
2. Install Acer Recovery Installer App
3. Backup my Recovery with the app
4. Install CWM with the app
5. Make a Backup with CWM
Is this a good/correct way to make a backup ?
What would be the best way ?
Thanks a lot for any useful input

king.mark said:
Hi fellow Android lovers
I'm still not sure how to make a proper backup of my completely stock A500 (HC 3.0.1).
My plan is:
1. Root with Gingerbreak
2. Install Acer Recovery Installer App
3. Backup my Recovery with the app
4. Install CWM with the app
5. Make a Backup with CWM
Is this a good/correct way to make a backup ?
What would be the best way ?
Thanks a lot for any useful input
Click to expand...
Click to collapse
Yes. This is EXACTLY what you should do but with a step 6 added.
Make a copy of your shiney new backups to seperate storage, such as your PC.

Cool ...
Thanks for answering.
Of cause I will safely store that backup on my PC.

A little bit more detail so you don't miss your original recovery.img:
Those interested in getting back their OTA, properly backing up their original ROMS or restoring them, please follow the tutorials in this thread:
Going back to stock TUTORIAL

Backup Help
I have rooted the device and installed the Acer Recovery app. Where's the backup function ? I can do the restore but how do I backup the device and cw install?
thanks,

you have to reboot into clockwork mod . Recovery .. then in there you can choose backup/recovery

Another thing to try and remember, if/when Acer Recovery updates with a new version of CWM - when you are putting this version on your device and updating recover, don't backup - it will overwrite your "stock" recovery backup with the previous CWM backup (which is likely not really needed with the new version of CWM) - leaving your only way back the final Acer Recovery option of "use stock <whatever version is included with that version of Acer recovery but may not match your recovery version>"
Learned that the hard way

pfc.joker said:
Another thing to try and remember, if/when Acer Recovery updates with a new version of CWM - when you are putting this version on your device and updating recover, don't backup - it will overwrite your "stock" recovery backup with the previous CWM backup (which is likely not really needed with the new version of CWM) - leaving your only way back the final Acer Recovery option of "use stock <whatever version is included with that version of Acer recovery but may not match your recovery version>"
Learned that the hard way
Click to expand...
Click to collapse
I can, however, confirm that the stock recovery they have still works in all versions of 3.1. Just ran into that with the 4.010.13 update.

Cannot fullbackup in CWM
Hi all,
I did as follow:
install Acer recovery installer V 1.5
click Clockworkmod recovery rev 1.3.4 by thor...
install recovery image (recovey image installed successfully)
power off
press power and volume button enter CWM mode
highlight backup and restore
highlight full backup
it reply
clockworkmod recovery v5.0.0.0 (thor...)
Fixing A500 boot/recovery checksums
running itsmagic
done!
can't mount /sdcard
I really need help from you
thanks in advance

mangolia said:
Hi all,
I did as follow:
install Acer recovery installer V 1.5
click Clockworkmod recovery rev 1.3.4 by thor...
install recovery image (recovey image installed successfully)
power off
press power and volume button enter CWM mode
highlight backup and restore
highlight full backup
it reply
clockworkmod recovery v5.0.0.0 (thor...)
Fixing A500 boot/recovery checksums
running itsmagic
done!
can't mount /sdcard
I really need help from you
thanks in advance
Click to expand...
Click to collapse
Do you have a working SD card inserted?

Yes, I have sdcard 16 gig from acer stock and external_sd memory card 8 gig, both of them work fine. I did remove external_sd card and repeat all steps it don't work...
Thanks

mangolia said:
Hi all,
I did as follow:
install Acer recovery installer V 1.5
click Clockworkmod recovery rev 1.3.4 by thor...
install recovery image (recovey image installed successfully)
power off
press power and volume button enter CWM mode
highlight backup and restore
highlight full backup
it reply
clockworkmod recovery v5.0.0.0 (thor...)
Fixing A500 boot/recovery checksums
running itsmagic
done!
can't mount /sdcard
I really need help from you
thanks in advance
Click to expand...
Click to collapse
To be clear, it has to be a working external micro SD formatted to fat32

Hi,
The code said can't mount /sdcard I think it is the 16 gig acer stock, it isn't extenal _sd card. My external_sd format FAT 32 it have music and film and
the tab read these files fine. Any idea ???

mangolia said:
Hi,
The code said can't mount /sdcard I think it is the 16 gig acer stock, it isn't extenal _sd card. My external_sd format FAT 32 it have music and film and
the tab read these files fine. Any idea ???
Click to expand...
Click to collapse
It is talking about the external, not internal. As for why its not working though I'm not sure

installed acer recovery installer but need premium to use backup. Doing a search i can find many referances to premium but nothing on how to get the premium version, can any one help?

jonhome2 said:
installed acer recovery installer but need premium to use backup. Doing a search i can find many referances to premium but nothing on how to get the premium version, can any one help?
Click to expand...
Click to collapse
I just used the acer recovery from the market and do my backup, don't know what you mean by premium as the regular works fine for backup.

[Q] Recovery installed to EMMC instead of SD

I did a search for 'boot recovery' and read a few thread going back to May, but none of them seem to quite fit what happened to me. If I have missed the instructions, please link to them and I'll check it out.
First the setup:
My NC is stock 1.2 on the EMMC. I then followed the instructions in the Size-agnostic SD Card image and CM7 installer for SD Cards. The only step I cheated on was copying both update-cm-7.0.3-encore-signed.zip and gapps-gb-20110613-signed.zip to the SD card after the card was imaged. The rom and gapps installed and work as intended.
Next it was my intent to install update-CM7-dalingrin-OC-sd-063011.zip for a little speed boost. But I couldn't get it to boot into recovery with the various hold this button timings and choosing reboot from the power button options. I then went into ROM Manager and Flash ClockworkMod recovery, which flashed 3.2.01 to the EMMC. I have confirmed that by removing my CM7 SD card and successfully booting to recovery.
So now what? I would have thought the Rom Manager should have flashed the CWM recovery to the SD card, as that is what I had booted from. How can I uninstall the CWM from EMMC and force it to installed to the SD card?
Thanks,
Zhin

Did you just say up there "which flashed 3.2.01 to the EMMC"? why did you expect it "should have flashed the CWM recovery to the SD card"?
Anyway, if you want to run from uSD, then anything related to eMMC or files that have "emmc" on file name, then ignore, discard it.
In your case, after you booted into recovery (using power button, and its options), you should be all set.
I don't now what makes you went into ROM Manager and flashed it

votinh said:
Did you just say up there "which flashed 3.2.01 to the EMMC"? why did you expect it "should have flashed the CWM recovery to the SD card"?
Click to expand...
Click to collapse
Because I thought that when you flashed a rom to the SD card and booted off the SD card it was treated the SD card as the 'local disk'. With the EMMC just being seen as additional storage when you where running off the SD. So when I booted from the SD card and opened Rom Manager while running from the SD card, I should think it would have flashed the CWM to the SD card.
votinh said:
Anyway, if you want to run from uSD, then anything related to eMMC or files that have "emmc" on file name, then ignore, discard it.
Click to expand...
Click to collapse
I didn't say anything about using files that said emmc in the OP.
votinh said:
In your case, after you booted into recovery (using power button, and its options), you should be all set.
Click to expand...
Click to collapse
The only way I can get to recovery is to remove the SD. How can I make sure to install update-CM7-dalingrin-OC-sd-063011.zip to the SD card? Can the SD card be put back in after booting to recovery?
votinh said:
I don't now what makes you went into ROM Manager and flashed it
Click to expand...
Click to collapse
When it wouldn't boot into recovery after the clean install from my OP, I started to look for other options. When I launched Rom Manager it said there was no recovery option installed.
-Zhin

Zhindel said:
I then went into ROM Manager and Flash ClockworkMod recovery, which flashed 3.2.01 to the EMMC. I have confirmed that by removing my CM7 SD card and successfully booting to recovery.
So now what? I would have thought the Rom Manager should have flashed the CWM recovery to the SD card, as that is what I had booted from. How can I uninstall the CWM from EMMC and force it to installed to the SD card?
Thanks,
Zhin
Click to expand...
Click to collapse
Rom Manager is useless for SD installs; just don't run it. It's not like most Android apps that only look at filesystem names (/sdcard, /emmc, etc), it uses the hardware device names (/dev/block/...) for its manipulations and pretty much assumes an emmc install.
Having CWM on emmc isn't a problem, it won't interfere with running the stock NC software from an emmc boot. I haven't run stock in forever, I don't know what they had for a recovery boot, but there are "restore to stock" threads that will show you how to find the parts if you want to put it back.
What were you intending to do by installing CWM? The recovery that comes with the SD install is what flashes new builds for you, so you don't want to mess with it. You can install CWM on the SD as an alternate boot instead of a recovery (uAltImg and uAltRam instead of uRecImg and uRecRam) and use the u-boot that comes with recent CM7 builds to boot it if you want to play with it.

stolenmoment said:
Rom Manager is useless for SD installs; just don't run it. It's not like most Android apps that only look at filesystem names (/sdcard, /emmc, etc), it uses the hardware device names (/dev/block/...) for its manipulations and pretty much assumes an emmc install.
Click to expand...
Click to collapse
Ahhh ha! That makes sense. I never knew that.
stolenmoment said:
Having CWM on emmc isn't a problem, it won't interfere with running the stock NC software from an emmc boot. I haven't run stock in forever, I don't know what they had for a recovery boot, but there are "restore to stock" threads that will show you how to find the parts if you want to put it back.
Click to expand...
Click to collapse
I can restore to stock easily enough. I have an image of the stock install for easy recover for just these circumstances.
stolenmoment said:
What were you intending to do by installing CWM? The recovery that comes with the SD install is what flashes new builds for you, so you don't want to mess with it. You can install CWM on the SD as an alternate boot instead of a recovery (uAltImg and uAltRam instead of uRecImg and uRecRam) and use the u-boot that comes with recent CM7 builds to boot it if you want to play with it.
Click to expand...
Click to collapse
The install instructions for the dalingrin kernels said they were CWM flashable. I wasn't going to get too fancy, but maybe I should look at some of the alternate boot options.
Thanks!
Zhin

I accidentally did the same exact thing before I realized VG included his own recovery on the SD. From what I've read, to uninstall CMW from the emmc, you need to create a separate CMW SD and do a full restore to stock.
http://forum.xda-developers.com/showthread.php?t=931720
As for putting CMW on the SD, IDK. VeryGreen's method of just appending "update-" to rom file names and placing them on the root of the SD has worked for me.

I didn't say anything about using files that said emmc in the OP.
Click to expand...
Click to collapse
Because you were confusing as indicated in your thread, I was just suggesting eliminating anything about "emmc" if you intended to run off uSD. I did not say you did it, I just recommend it. For instance, Dalingrin OC kernel, there are several versions out there and anything with "emmc", then you should ignore them. That's all
I can restore to stock easily enough. I have an image of the stock install for easy recover for just these circumstances.
Click to expand...
Click to collapse
I assume you are all set.
Am I right? or still need help

I did the same thing and am too wondering how to remove it for warranty purposes. My Nook came w/ 1.2...does that mean 'd have to restore to stock 1.0.1 and then upgrade to 1.2?

dna59 said:
I did the same thing and am too wondering how to remove it for warranty purposes. My Nook came w/ 1.2...does that mean 'd have to restore to stock 1.0.1 and then upgrade to 1.2?
Click to expand...
Click to collapse
Get one of those 2
http://forum.xda-developers.com/showthread.php?t=1050520

Broke my recovery

Nook was running cm7
I went here http://forum.xda-developers.com/showthread.php?t=958748 and downloaded recoveryfix.zip and installed it
that was silly
now nook is stuck at book
How can I reflash cwm 3.0.2.8?

mrkkk said:
Nook was running cm7
I went here http://forum.xda-developers.com/showthread.php?t=958748 and downloaded recoveryfix.zip and installed it
that was silly
now nook is stuck at book
How can I reflash cwm 3.0.2.8?
Click to expand...
Click to collapse
Do you remember what version of the stock OS you had before you installed CM7? What happened, was that file that you downloaded is specific to a version of the stock OS.
Make yourself a bootable CWM card by following the directions HERE
Then download the attached file that goes with your stock OS version, and put it into the root of the CWM card.
Boot the device with that card, and flash the file. Remove the SD card when done, and reboot. You should now be back into your CM7. At this point to can flash CWM back onto the NC, or leave it off.

GMPOWER said:
Do you remember what version of the stock OS you had before you installed CM7? What happened, was that file that you downloaded is specific to a version of the stock OS.
Click to expand...
Click to collapse
Any way to determine that now?

mrkkk said:
Any way to determine that now?
Click to expand...
Click to collapse
Not really, the version 1.1.0 update came out at the end of January, and the guide that you linked to was made in February, so I would say that there is good chance that you were not on version 1.1.0. I would start with the 1.2.0 package, and work my way down.

No luck
Got meself a monster root pack - http://code.google.com/p/monster-rootpack/downloads/list
1.2.0 and 1.1.0 gave me install failed after rebooting
1.0.1 its still stuck at "Touch the future of reading"
Dont I want to flash a good copy of CWM back so that it can boot cm7?

mrkkk said:
No luck
Got meself a monster root pack - http://code.google.com/p/monster-rootpack/downloads/list
1.2.0 and 1.1.0 gave me install failed after rebooting
1.0.1 its still stuck at "Touch the future of reading"
Dont I want to flash a good copy of CWM back so that it can boot cm7?
Click to expand...
Click to collapse
The NC does NOT need CWM installed on the device to install or run CM7. A lot of people don't install it because of problems like this. I just did a restore of my CM7 image, and took the same steps as you. When it reboots and says install failed, I just shut it down and restarted right back into CM7.
The problem with the package that you had started with was the fact that besides the recovery files it installed a version of u-boot.bin that does not seem to be compatible with your device. The packages that I put up include each version specific u-boot.bin and recovery files.
I would flash the 1.2.0 file again, this time when it restarts and says install failed, just reboot the device, and it should go into CM7. At the very least, at this point you could do a full factory restore.

Update
before seeing your last message I built cwm 3.2.0.1 card using http://www.techerrata.com/dl.php?path=15&file=1gb_clockwork-3.2.0.1-eyeballer.zip
downloaded cm7 latest nightly
flashed it
applied titanium backup
was up in about an hour
BTW I do like CWM recovery, I can take nandroid backups time to time
Thanks for helping

[Q] Installing CWR on nook

I'm trying to find out if there is a way to install clockwork recovery on to the nook itself. I can boot it up with an sd card, but since I want to put muiu on the nook, it seems like a good idea to have recovery on the nook.
There don't seem to be any link to the latest version of cwr in the development thread, and it has been a couple of weeks since someone posted there asking for a link, but never got a reply.
I guess what I'm really looking for is a .zip of the latest clockwork recovery that I can install on the nook through the clockwork recovery I have on my sd card.
Any help, as always, is greatly appreciated!

Go to ROM manager in applications and select Flash CWM Recovery. It'll install to the emmc.

416inversed said:
Go to ROM manager in applications and select Flash CWM Recovery. It'll install to the emmc.
Click to expand...
Click to collapse
He's running off an SD card. ROM Manager only works with internal installations.
To the original poster: Once you flash CWR to the eMMC you no longer have a stock Nook for the purposes of warranty. Why not just go all the way and put CM7 on the eMMC? You can follow the directions here: http://mrm3.net/nook-color-how-to-install-cyanogenmod-nightlies/
Make sure you choose the newest version of CWR (v3.2.0.1) when you do this!

patruns said:
He's running off an SD card. ROM Manager only works with internal installations.
Click to expand...
Click to collapse
Yeah, but CM7 on SD still has ROM Manager installed. OP wants to put CWM on the emmc. Hitting the "Flash CWM Recovery" selection in ROM Manager will put the latest CWM on their emmc. (I know it does, because I was noob enough to accidentally do it to my own Nook).
But that's what Crwly was asking about, right?

I am dual-booting CWR and CM7, both off the microSD. I used verygreen's installer to put CM7 on the microSD first, then installed racks11479's modified CWR. This does not satisfy ROM Manager, but it does let you backup, restore, and install zip packages off your 4th partition.
EDIT: Oh, and you do need another microSD to boot CWR, before you could use it to "flash" CWM SD Dualboot 0.1 to your current microSD.

[Q] NC 1.2.0 bricked. Need to restore and start over.

I just bought an NC 1.2.0
no need to bore anyone with details but it is safe to say that it is virtually bricked. i would love a surefire way to get it completely back to the stock to start all over again.
i tried the repartitioning and reformatting technique using cm7 without any luck whatsoever. when i boot the device gets to the big N and "contains Reader mobile technology..." screen and never fully boots.
does anyone have a solution?

Presumably, one of those boring details involved writing an image to an SDcard:
eyeballer said:
Download 1gb CWM 3.2.0.1 sdcard image from here. MD5 of .zip: 1319739d33642ed860e8044c3d55aa56. (I made this based on work in this thread. credit: to cmstlist and DizzyDen, and kevank for hosting). You really only need the 1gb image ... no matter what the size of your card is. A smaller image will burn faster, and when you're done with the guide you can reformat the card anyway.
Click to expand...
Click to collapse
There's a decent chance the problem with your install is that you were using an older version of CWM on a newer NC, and it didn't write all the partitions correctly. Regardless, get the current version now.
Grab a B&N 1.2 image:
nemith said:
I modified the official 1.2 update to allow CWM to flash them. You can use these to upgrade to 1.2 or to return to stock.
There are two files. One replaces CWM with the stock recovery (good for going back to stock). The other doesn't replace CWM (but will replace uboot).
Other than that they are identical to the update from B&N.
update-nc-stock-1.2-keepcwm-signed.zip
update-nc-stock-1.2-signed.zip
Please note neither one of these are rooted yet.
Click to expand...
Click to collapse
and install zip from sdcard > choose zip from sdcard in CWM.

Another option, if will at least start to boot, is to start the boot process and then hold the power button down to shut it off. Repeat this 8 times in a row and the unit will initiate a self restore to the way it was shipped.
One thing to remember is that if you have a blue dot on the box for the nook, it has a different partition size and must be accounted for when installing CM7.

mvnsnd said:
Another option, if will at least start to boot, is to start the boot process and then hold the power button down to shut it off. Repeat this 8 times in a row and the unit will initiate a self restore to the way it was shipped.
One thing to remember is that if you have a blue dot on the box for the nook, it has a different partition size and must be accounted for when installing CM7.
Click to expand...
Click to collapse
If he has CWM on his internal recovery partition, I don't think 8 failed boots will work.
Also, the latest version of CWM can install CM7 correctly regardless of partitioning, though the old-style partitions are going to be preferable for most people running CM7.

Taosaur said:
If he has CWM on his internal recovery partition, I don't think 8 failed boots will work.
Also, the latest version of CWM can install CM7 correctly regardless of partitioning, though the old-style partitions are going to be preferable for most people running CM7.
Click to expand...
Click to collapse
Ah. I did not know that CWM installs on the internal recovery partition. Thanks.

mvnsnd said:
Ah. I did not know that CWM installs on the internal recovery partition. Thanks.
Click to expand...
Click to collapse
It does if you flash it from ROM Manager, regardless of whether you have ROM Manager running internally or on a CM7 SD install. If he hasn't done that, 8 failed boots should work, but I'm not 100% sure on a repartitioned device.