Database Users

Backup Recovery image

Hi I have read posts about backup using Nandroid on 32a for system and data. so how about if i want to backup the original recovery img before flashing it to cyanogen's or RA's?
Thanks in adv.

Bump
anyone?
thx in adv

if im understanding correctly all you want is the original recovery, you can download it as the .img file then just save it to your computer and install it like ra/cyan if you ever want to go back to it
you wouldn't necessarily need to make a backup of it just like you don't need a backup of the original android software you can download the ota releases and install them like a rom
the reason it has the back up is to keep your last working rom in case you install one with problems
I hope that helped I tried to answer the question a few different ways for you

One-Click-Root method.
The application, "Recovery Flasher" can do exactly what you desire. Although, if you're currently operating on the 1.6 firmware; you'll need to "back track" to 1.5 and go about the rooting process normally.

[Q] Stock nandroid

So I have been trollin through a bunch of threads and searching before I ask. I am rooted running Stupidfast v1.23 and jt super clean rom on DI01. I was reading through flashing back to stock package via oden, but i noticed you need a stock nandroid recovery. I currently have CW. Do I need to get the stock nandroid or just flash the package?
If this has been asked a million times, I am sorry. Please direct me where to go.

Anyone?? There has to be an answer out there somewhere...

I believe if you go to the development forum and check the stickies there a post with the Odin to stock info that has the stock nandroid in it. I think that's where it is - I go to so many forums I can never remember where I saw what. I'm on my phone right now but I will check later to make sure.
Sent from my SCH-I500 using XDA App

You don't need a nandroid backup if you just want to go back to stock.
http://forum.xda-developers.com/showthread.php?t=782204
Or, flash adrynalyne's DI01 Odin package to get you back to 2.1-update1.
http://forum.xda-developers.com/showthread.php?t=867648

Stock nandroid is in the dev forum. Probably a few pages in though.

I'm retarded. I meant to say do i need a stock recovery (not stock nandroid) or does the package provide all of it.

A Nandroid backup is just a backup image taken through CW Recovery. You can't have one without the other (at least, not on this phone -- some other devices have different custom recovery tools you can choose to use)
But that doesn't matter anyways, because Odin flashes work regardless of what you have or don't have on your phone. It's like restoring Windows from a recovery disk -- it wipes and replaces everything. That'd be why it's named after a god. Doesn't matter if you're rooted, doesn't matter if you have CWR installed, it'll wipe the slate clean and start you off fresh.
P.S. I'm not sure "trollin" means what you think it means. If you'd gone trolling in a bunch of threads, it's highly unlikely anyone would help you.

Trolls smell bad, live under bridges, and cause hazard to passers thorough. I knew what you meant.
You wanted a stock nandroid recovery. That brings your phone back to before you messed it up. Nandroid is a backup program that is run via Clock Work Recovery (which can be run from recovery mode - to run, flash a special clockwork recovery in odin, install rom manager app, run that, click the install button which in turn downloads and copies an update.zip file to the root of your sd card, then from recovery mode *vol +&- while powering up* you ' install' update.zip which essentially runs it)
You run nandroid from therein... or from the Rom Manager front end.
Actually you would run it, except you cannot.
# Nandroid is a BACKUP program. You need to have made your own image before hand for it to be helpful! #
However, thanks to Adrynalyne, you have another option for restoring your phone to stock:
http://forum.xda-developers.com/showthread.php?t=867648
A caveat. It is a large file, and somewhat of a strain to host. You only need to use it if your phone is totally borked and you do not know what else to do. Otherwise, you can often repair your woes by opening up CWR and using the clear data commands (which do not touch the sd card) & the install from sd card option, which in turn lets you find a rom you previously installed on your sd card and rerun it. Unless of course you installed voodoo, in which case you need a whole other thread before proceeding....
SIDE NOTE: Here its the classic piecewise restore I used back in the day, which includes stock kernel, stock system rom, and Odin:
http://forum.xda-developers.com/showthread.php?t=782204
Unfortunately the only di01 (first vzw updated modem) posted publicly is the one in the first link. If you need to replace your modem/radio/baseband, then you need to find dj05 separately, or simply have used adrynalyne's restore (linked up top) in the first place.
However, when you do get your phone back to happy - my tired finger asks you to do just one thing:
Run the "Backup Current ROM" option the moment you install Rom Manager - or don't install it!
Swyped w/ XDA App. When in doubt, mumble. Nandroid: Don't use Rom Manager without it.

Need serious help - to get my phone back to work

Hi,
My DHD is not working after a update.
I am not sure what to do now...
I have cyanogenmod 7 and When I bought it it was rooted and with S-OFF.
Today I would try to get mod with Sense 3.0 on My phone.
Actually I will get it back to Factory settings, but I not know how to go on now...
It starts up and run into the boot picture with the cyanogenmod 7 and stops and start over countiuosly.
Please help me to get further.

I got it back to work, but are there someone who can help me to get it like this
htc product legend
with the clock and the dock.

Welcome to XDA mate.
You have to know some basic stuff before flashing any ROM.
1. ClockworkMod recovery and how it works.
2. Find a ROM that you like and download it.
3. Follow the instructions written on that ROM for flashing via ClockworkMod recovery and you are done.
If you are looking for stock HTC look, you must download a Sense ROM (CyanogenMod is an AOSP ROM) and there are many of them. I would suggest reading from this post, it helped me a lot when I was new to the android scene.
If you have any questions please post here and I am sure people would be happy to help.
Remember... Search function is your friend here in XDA.
Cheers

Oh, yhea - what link you gave me there, thanks.
Could you please guide me throw my first mod. I have desited it should be this one
http://forum.xda-developers.com/showthread.php?t=1056727
Kernel - LeeDrOiD V3.2.1 - 2.6.35.13 Revised - BFS
You problably know the first time, you do this it a good ide to have some back up from anotherone who have try it before...

1.Download all files mentioned below and copy them to the root of your SD card
a. Wipe file
b. Rom File
2. Boot to ClockworkMod recovery
3. Backup your current Rom to your SD
4. Flash the Wipe file (Install Zip file from SD card option)
5. Flash the Rom file (Install Zip file from SD card option)
6. Eat a donut! (aka wait for 10-15mins)
7. You should be done.
If things go wrong, you can always restart in ClockworkMod recovery and restore your previous Rom.
Cheers

I made a nandroid with ROM Manager, and now when I need to restore it, CWM says MD5 mismatch. What did I do wrong?

ViDtje said:
I made a nandroid with ROM Manager, and now when I need to restore it, CWM says MD5 mismatch. What did I do wrong?
Click to expand...
Click to collapse
Hmmm did you attempt to move or edit the nandroid backup? As far as I can tell, if you have nothing to boot too, then your best bet would be the same as instructions below, to boot recovery, mount sd, put new rom on there super wipe, and flash new rom
Thanks button always appreciated!

naailalzuhir said:
1.Download all files mentioned below and copy them to the root of your SD card
a."Not allowed ex link"
b. "Not allowed ex link"
2. Boot to ClockworkMod recovery
3. Backup your current Rom to your SD
4. Flash the Wipe file (Install Zip file from SD card option)
5. Flash the Rom file (Install Zip file from SD card option)
6. Eat a donut! (aka wait for 10-15mins)
7. You should be done.
If things go wrong, you can always restart in ClockworkMod recovery and restore your previous Rom.
Cheers
Click to expand...
Click to collapse
Ohh, how easy it was. Tanks a lot. That was great you could simplyfied it to that level.

I think it went wrong because I did it with ROM manager. Recovery, it all went right.
Sent from my Desire HD using xda premium

ViDtje said:
I made a nandroid with ROM Manager, and now when I need to restore it, CWM says MD5 mismatch. What did I do wrong?
Click to expand...
Click to collapse
Md5 mismatch means that image is likely to be corrupt.
Google and download the md5 checker s/w. Check the md5 hash with the one posted on the forum/website where you are downloading the image.
If needed redownload the image and check the md5 hash again.
Once the md5 hashes match you may proceed flashing the image on to the phone.

[RECOVERY - 1.2] ClockworkMod 5.5.0.4 Touch Recovery - TEAM DRH

CLICK PIC FOR TEAM HOMEPAGE​
ClockworkMod 5.5.0.4 Touch Recovery - TEAM DRH (Update 03/05/12)
This version of ClockworkMod Recovery is based on version 5.5.0.4 and has the following "perks:"
Touchscreen
Capacitive buttons can select, move up/down, and go back
Download:
http://teamdrh.com/DRH-Downloads/Touch_Recovery/CWMR_Touch_5504_B15_normalfont_DRH.img (NVFLASH)
http://teamdrh.com/DRH-Downloads/Touch_Recovery/CWMR5504_recovery_B15.zip (Flashable Zip)
How to Install:
There are 2 ways to install. Either run the update through the "CWMR5504_recovery_B15.zip" file or use the "CWMR_Touch_5504_B15_normalfont_DRH.img" image if you will be flashing it with NVFLASH.
NVFLASH Command
To flash use the following commands:
Code:
nvflash --bl bootloader.bin --download 9 CWMR_Touch_5504_B15_normalfont_DRH.img
Changelog:
Added DRH logo
Roboto Font
Changed Mount UDB Storage to the /EMMC
Added the option to format the internal sdcard /emmc
Fixed the magic number mismatch issue
Ability to select update from External SDCard or Internal SDCard
Made internal/external partitions clear
Fixed reboot recovery loop
Allowed the /misc partition to be formatted incase you get stuck in a reboot recovery loop
Swap size bug fixed
Kanged commits to fix the UI overlapping the buttons
Removed /misc (fixes hanging at birds)
Switched from stock Viewsonic kernel to Pershoot's
To Do:
Proper reboot into CWM Recovery
More will be added to the list as more bugs are encountered (if any)
How to Perform a Backup
For those wanting to do backup. Here is the step by step on how to get it to work until a proper fix is done (thanks raj...didnt' understand what you were were saying at first):
REMOVE external sd
Boot to CWMR
Go to "mounts and storage" & select "mount /sdcard" (this is what I didn't understand..how internal could be seen as /emmc & /sdcard)
go back to main menu & select "backup and restore"
select "backup to internal sd"
watch backup complete (including .android_secure on the internal sd)
Thanks to AlAbbo for the instructions!
For the people who wonder what this does:
http://www.youtube.com/watch?v=bGKahQaJadQ
Ported to the G-Tablet by Plastikman
-based on CWM from Koush
-Other credits: gweedo767, cennis91, utkanos
-Original Google+ project page here

Reserved for future use.

I think this was a great idea...nice job...
i have clock work 5.0.2.7...something like that...and wen i install ur zip it works....pull battery...gor right cack into recovery...and its not urs anymore...where can i get clockworkmod 5.5.0.4...so then it willl stay on...i guess i need an update of clock work mod recovery...can you help me out...thanks in advance... ;-)

Guys
I am stuck in a recovery boot loop
How do you fix this?

chief1978 said:
Guys
I am stuck in a recovery boot loop
How do you fix this?
Click to expand...
Click to collapse
Fixed with nvflash

guys,
will this CWM 5.5.0.4 work for update froyo / gingerbread rom also?
currently i'm still using beasty rom (froyo) and thinking to try ICS rom
but if i don't like it, i might want to restore using thisCWM 5.5.0.4
from backup which i have created using CWM 3.0.2.8
is it doable like this?

dony71 said:
guys,
will this CWM 5.5.0.4 work for update froyo / gingerbread rom also?
currently i'm still using beasty rom (froyo) and thinking to try ICS rom
but if i don't like it, i might want to restore using thisCWM 5.5.0.4
from backup which i have created using CWM 3.0.2.8
is it doable like this?
Click to expand...
Click to collapse
ROM backups need to be backed up and restored with the same version of CWM.
Sent from my ICS powered g-Tablet using XDA Premium.

rmarinella said:
ROM backups need to be backed up and restored with the same version of CWM.
Click to expand...
Click to collapse
Not necessarily.

rajeevvp said:
Not necessarily.
Click to expand...
Click to collapse
Should I change that to should be backed up and restored with the same version? It's not fun to find out a backup won't restore due to incompatibility.
Sent from my HTC Thunderbolt using xda premium.

rmarinella said:
Should I change that to should be backed up and restored with the same version? It's not fun to find out a backup won't restore due to incompatibility.
Sent from my HTC Thunderbolt using xda premium.
Click to expand...
Click to collapse
Should is a better word. I have seen backups restored w/ different versions of CWM but I have also seen them fail due to different revisions.

rmarinella said:
Should I change that to should be backed up and restored with the same version? It's not fun to find out a backup won't restore due to incompatibility.
Click to expand...
Click to collapse
fosser2 said:
Should is a better word. I have seen backups restored w/ different versions of CWM but I have also seen them fail due to different revisions.
Click to expand...
Click to collapse
There is no incompatibility for backups/restores between CWM versions 2.x, 3.x and 4.x. Both the filenames and the contents of the backup files will be the same. Try it: load each of them in turn, do a backup in each, and look at the nandroid.md5 file produced. Apart from the cache.img and recovery.img files, all the other MD5 sums will be the same.
There are 2 minor incompatibilities with CWM-5.x which only come up when you create a backup in CWM-5.x and then try to restore in one of the older CWM versions. (Going the other way is no problem--ie. CWM-5.x will happily read and restore the backup files created by all the older versions of CWM.):
1. File formats. The contents of /data and /sdcard/.android_secure are now in tar files instead of the old yaffs2 image files.
2. Filenames. The backup filenames have changed from partition_name.img to partition_name.fstype.ext.
To fix the first incompatibility, you can add a ro.cwm.prefer_tar=false line to the /default.prop file in CWM. With this change, CWM-5.x will create the exact same backup files (yaffs2 images) that the other CWM versions also output.
The second incompatibility you can just as easily fix by removing the "fstype." from the backup filenames created by CWM-5.x, and then changing the names to suit in the nandroid.md5 file.

rajeevvp said:
There is no incompatibility for backups/restores between CWM versions 2.x, 3.x and 4.x. Both the filenames and the contents of the backup files will be the same. Try it: load each of them in turn, do a backup in each, and look at the nandroid.md5 file produced. Apart from the cache.img and recovery.img files, all the other MD5 sums will be the same.
There are 2 minor incompatibilities when it comes to CWM 5.x.
1. File formats. The contents of /data and /sdcard/.android_secure are now in tar files instead of the old yaffs2 image files.
2. Filenames. The backup filenames have changed from partition_name.img to partition_name.fstype.ext.
To fix the first incompatibility, you can add a ro.cwm.prefer_tar=false line to the /default.prop file in CWM. With this change, CWM-5.x will create the exact same backup files (yaffs2 images) that the other CWM versions also output.
The second incompatibility you can just as easily fix by removing the "fstype." from the backup filenames created by CWM-5.x, and then changing the names to suit in the nandroid.md5 file.
Click to expand...
Click to collapse
What you've stated should be the case. However, I have had issues with compatibility between versions. Bottom line is we should point newer users to proven successful methods that will eliminate most challenges. Following one common procedure for each upgrade, backup and restore accomplishes this.
Sent from my HTC Thunderbolt using xda premium.

Bottom line is we should point newer users to proven successful methods that will eliminate most challenges. Following one common procedure for each upgrade, backup and restore accomplishes this.
Click to expand...
Click to collapse
Very admirable--if a little vague. All of these are "proven successful methods that will eliminate most challenges". In Q&A format:
Q. Can I backup in CWM-2.x and restore using CWM-{3,4,5}.x?
A. Yes.
Q. Backup in CWM-3.x and restore using CWM-{2,4,5}.x?
A. Yes.
Q. Backup in CWM-4.x and restore using CWM-{2,3,5}.x?
A. Yes.
Q. Backup in CWM-5.x and restore using CWM-{4,3,2}.x?
A. No, but it's possible.
There is only one case which doesn't work. None of the other cases will cause problems.
rmarinella said:
However, I have had issues with compatibility between versions.
Click to expand...
Click to collapse
Which specific versions of CWM and while doing what precisely? Except in one case, the files created (and understood) are exactly the same, so no incompatibility can exist between versions as far as backups and restores are concerned.

rajeevvp said:
Very admirable--if a little vague. All of these are "proven successful methods that will eliminate most challenges". In Q&A format:
Q. Can I backup in CWM-2.x and restore using CWM-{3,4,5}.x?
A. Yes.
Q. Backup in CWM-3.x and restore using CWM-{2,4,5}.x?
A. Yes.
Q. Backup in CWM-4.x and restore using CWM-{2,3,5}.x?
A. Yes.
Q. Backup in CWM-5.x and restore using CWM-{4,3,2}.x?
A. No, but it's possible.
There is only one case which doesn't work. None of the other cases will cause problems.
Which specific versions of CWM and while doing what precisely? Except in one case, the files created (and understood) are exactly the same, so no incompatibility can exist between versions as far as backups and restores are concerned.
Click to expand...
Click to collapse
How confrontational! Sorry, I don't keep logs.
Sent from my HTC Thunderbolt using xda premium.

rmarinella said:
How confrontational! Sorry, I don't keep logs.
Click to expand...
Click to collapse
Nope. Helpful, actually. Meant specifically to help answer questions like this one.

Originally Posted by chief1978 View Post
Guys
I am stuck in a recovery boot loop
How do you fix this?
Fixed with nvflash
Can I get some clarification on this? I flashed with nvflash successfully but I'm stuck in a boot loop.

hungsohlo said:
Can I get some clarification on this? I flashed with nvflash successfully but I'm stuck in a boot loop.
Click to expand...
Click to collapse
What kind of boot loop?
For an ordinary kind of boot loop, simply boot into CWM and do a "wipe data/factory reset".
For a recovery boot loop see this thread.

I've tried nvflash and the .zip file. I can not boot back into recovery after installing this CWM. Was originally on CWM v08.

same as the above poster
Also whenever I use NvFlash to go back to stock it works correctly but any attempt to flash another rom and it just sits at the 3 birds screen. When I try to flash this and go back into CW recovery it just says booting to kernal image.
---------- Post added at 02:46 PM ---------- Previous post was at 02:02 PM ----------
Forgot to mention earlier - my currect CW version is 2.5.1.1

genei.09 said:
I've tried nvflash and the .zip file. I can not boot back into recovery after installing this CWM. Was originally on CWM v08.
Click to expand...
Click to collapse
hungsohlo said:
Also whenever I use NvFlash to go back to stock it works correctly but any attempt to flash another rom and it just sits at the 3 birds screen. When I try to flash this and go back into CW recovery it just says booting to kernal image.
---------- Post added at 02:46 PM ---------- Previous post was at 02:02 PM ----------
Forgot to mention earlier - my currect CW version is 2.5.1.1
Click to expand...
Click to collapse
Both of you have the same problem. You have a 1.1 bootloader, but, this version of CWM has a kernel built to run on a 1.2 bootloader (this is indicated in the thread title, actually).
Use one of the versions of CWM with a 1.1 kernel in it. See this thread.

CWM-Rom manager not working on N7 JB 4.2.1

Is anyone else having loads of problems with clockwork mod and rom manager since updating to 4.2.1
For me RM doesnt do anything and I CWM keeps will not re-flash a backup unless its 4.2.1. Even though I copy n past to new directory where CWM keeps backups but will not reflash them. Also everytime after I use CWM it seems to delete itself and i have to reflash via the command line. Help welcome. Thx in advance....
Update: Not sure if its RM or CWM. Have just worked out CWM is deleting itself everytime after use. IT doesnt leave any other option once you try to re-boot device from CWM....

veroby said:
Is anyone else having loads of problems with clockwork mod and rom manager since updating to 4.2.1
For me RM doesnt do anything and I CWM keeps will not re-flash a backup unless its 4.2.1. Even though I copy n past to new directory where CWM keeps backups but will not reflash them. Also everytime after I use CWM it seems to delete itself and i have to reflash via the command line. Help welcome. Thx in advance....
Update: Not sure if its RM or CWM. Have just worked out CWM is deleting itself everytime after use. IT doesnt leave any other option once you try to re-boot device from CWM....
Click to expand...
Click to collapse
There's a file in /system that you should either rename or delete called: recovery-from-boot.p
That reloads the stock Android recovery at each reboot. Then once you have renamed/deleted it, reflash CWM Recovery again from the command line and it should stick now.
You're using the latest CWM Recovery correct? I don't use RM or CWMR at all (TWRP), so I may not be able to totally help out.

RMarkwald said:
There's a file in /system that you should either rename or delete called: recovery-from-boot.p
That reloads the stock Android recovery at each reboot. Then once you have renamed/deleted it, reflash CWM Recovery again from the command line and it should stick now.
You're using the latest CWM Recovery correct? I don't use RM or CWMR at all (TWRP), so I may not be able to totally help out.
Click to expand...
Click to collapse
Hey thx - I have always used them and found them to be easy tools in the past. Dont really want to change to TWRP but it seems all recommendations are leaning towards and its the way to go with 4.2.1. Thx again... I have to ask why that file exist in the first place. Just to catch donkeys like me out.....Also if you know and are still around. Is there a way to restore old backups from 4.1.1

veroby said:
Hey thx - I have always used them and found them to be easy tools in the past. Dont really want to change to TWRP but it seems all recommendations are leaning towards and its the way to go with 4.2.1. Thx again... I have to ask why that file exist in the first place. Just to catch donkeys like me out.....Also if you know and are still around. Is there a way to restore old backups from 4.1.1
Click to expand...
Click to collapse
I've had no issues flashing 4.1.1/4.1.2 ROMs to 4.2.1 and vice versa...but again I'm using TWRP Recovery.
The file is in the stock images from Google, and it's there to reload stock Android recovery at boot...other than that I'm not sure of the exact reasoning.
I know that Android 4.2 has multi-user support, and that has been the cause for many issues with 4.2 in general due to it creating a folder /sdcard/0...so flashing multiple 4.2 ROMs without the latest CWM Recovery version 6.0.1.9 would cause another folder created there at /sdcard/0/0...and so on. If you created another user, they would have their own folder at /sdcard/1...and so on.
I would make sure that you have the latest CWM Recovery flashed to your device, then put your backup in the correct folder. From what I remember when using RM and CWM, there's the folder for your backup and then one level up from that there's the blobs folder, you'll need BOTH of those in order to restore things, as the blobs folder is the backup.