Does anyone know exactly what it is that breaks the backups. When I say "break" you try to restore and get the message to use ADB. I had backups that I know worked because I had used them, I flashed the beta of Warm 2.2 RLS 3, tried to restore and every single one was broken after that. Just trying to figure out what is causes this. Or I may be the only one, who knows.
I've had md5 mismatches which won't let me restore a nand backup. Don't know why.
Sent From My HTC Evo 4G Using Tapa Talk Pro!
cornelious1212 said:
Does anyone know exactly what it is that breaks the backups. When I say "break" you try to restore and get the message to use ADB. I had backups that I know worked because I had used them, I flashed the beta of Warm 2.2 RLS 3, tried to restore and every single one was broken after that. Just trying to figure out what is causes this. Or I may be the only one, who knows.
Click to expand...
Click to collapse
Are you using ClockWorkMod or AmonRA?
AmonRa. 10 char
cornelious1212 said:
AmonRa. 10 char
Click to expand...
Click to collapse
Did you use rom manager to flash back clockwork at any point using amon ra?
i get errors when backing up and restoring when the battery or storage space on the sd card is low.
i've also seen nand restores fail when trying to restore using a different hboot than the one used to make the backup.
hope that helps.
Have you changed the filename? Also check storage space. I got an error only once and that was when I changed file names. I usually change the end of name to whichever rom it was but I accidentally put a space.
bizdady said:
Have you changed the filename? Also check storage space. I got an error only once and that was when I changed file names. I usually change the end of name to whichever rom it was but I accidentally put a space.
Click to expand...
Click to collapse
I had changed the file name, but I had used that backup many times before. Not really sure what the deal is.
Changing the file name most of the time hurts the nandroid backup because both folders together are in sync in the checksums. That's why it creates two folders. This is what I was told. That's why they are brokem
Sent from my PC36100 using XDA App
Have changed your hboot to try cm since you made those backups?
Sent from my blah blah blah blah
Changing hboot wont do anything.....well it well, but I went throught the same thing and I never changed hboot. If you tried to boot pc36.Img, then ya, it messed them up. But even changing the file names, messes the checksum up
Sent from my PC36100 using XDA App
bmxerkid954 said:
Changing hboot wont do anything.....well it well, but I went throught the same thing and I never changed hboot. If you tried to boot pc36.Img, then ya, it messed them up. But even changing the file names, messes the checksum up
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
What I meant was that if he made his backups, then changed his hboot for any reason (like to try cm), then he won't be able to restore those backups until he goes back to the hboot version he had when he made the backups.
Sent from my blah blah blah blah
Right right. These no doubt there that if he changes the version, it wont work. But if then, reverting back may not even solve it. But lets say he didn't downgrade or even upgrade hboot, then what's left?
Sent from my PC36100 using XDA App
You're right, but you and the other posters already seemed to be addressing the other options pretty well. Just wanted to throw it out there
Sent from my blah blah blah blah
I also had this issue where I was able to sucessfully backup and restore, however the restored rom was missing a lot of files and apps and didn't look right. I wasn't able to backup anything for quite a while, and then I updated the recovery image to the latest Amonra version. This seemed to correct it, as I just did a sucessful backup and restore. Hope it helps.
Related
Can you delete a rom off your sd card after youve installed said rom and done a nandroid backup? will that backup still bootup and run correctly
If you talking about the actual ROM zip file then yes you can delete it. If you are talking about deleting other Nandroid backups yes you can. Just make sure you don't delete the most recent nand backup.
thank you sir
I usually like to keep my ROM on my SD card so if something goes wrong, at least I have it. The only time this practice has ever been useful was when I flashed Amon Ra and tried to flash a new ROM. Went into bootloops and found out the hard way that Clockwork nand backups don't work with Amon Ra. Because I had my ROM, I fixed it easily.
Just my two cents. Nandroids usually do the trick, though.
Sent from my PC36100 using XDA App
I usually keep 2 nand backups on my SD card 1 stock sense and 1 of my current rom. If I have any other roms Ill just save them to my pc to keep room in the sd card clear.
finding this out now flashed amon ra 1.8 and doesnt see any downloaded roms on sd card, rebooted phone and i have no service. working off wifi only, rom manager is gone and I cant access the market to download ,any ideas
"the process com.android.phone has stopped"
Do you have Rom Manager? If so you can try flashing ClockworkMod...
Sorry, just reread your post...
cbrewington75 said:
finding this out now flashed amon ra 1.8 and doesnt see any downloaded roms on sd card, rebooted phone and i have no service. working off wifi only, rom manager is gone and I cant access the market to download ,any ideas
"the process com.android.phone has stopped"
Click to expand...
Click to collapse
Place the ROM on the root of your SD card. It must not be in your download folder.
I learned my lesson today and will always keep a zip of a rom on my card. The latest version of clockwork was a bust. I couldn't use my phone for almost 2 days. Thank god I fixed it.
Sent from my PC36100 using XDA App
gqstatus0685 said:
I learned my lesson today and will always keep a zip of a rom on my card. The latest version of clockwork was a bust. I couldn't use my phone for almost 2 days. Thank god I fixed it.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This is why I keep my ROM on my SD card. Glad you fixed it, man.
Sent from my PC36100 using XDA App
OK. so what happens if you are running beliEVO and then flash Cyanogen. Can you restore a backup from a previous ROM without bricking the device? And if you can will app data be there?
Pacothebandit said:
OK. so what happens if you are running beliEVO and then flash Cyanogen. Can you restore a backup from a previous ROM without bricking the device? And if you can will app data be there?
Click to expand...
Click to collapse
If you had done a nandroid backup of the beliEVO rom before flashingCyanogen rom, then yes, your can restore the backup and all the apps will be there.
But it's always a good thing to backup the apps before flashing a new rom.
Sent from my PC36100 using XDA App
bigmoogle said:
If you had done a nandroid backup of the beliEVO rom before flashingCyanogen rom, then yes, your can restore the backup and all the apps will be there.
But it's always a good thing to backup the apps before flashing a new rom.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Awesome. Same rules apply if it was not specifically a Nandroid? I used ROM manager prior to flashing Cyanogen.
This is a helpful thread, i was also wondering this...
I have a question, can I rename my nandroid backups on my SD card so I know which backups are which?
Also, sorry to sorta hijack your thread, but I backup my apps with mybackup, and data with titanium, but how do I restore that info if/when I flash a new rom? I'm using cm6 and loving it but would like to try more... thanks!
Sent from my PC36100 using XDA App
yes, you can rename backups for both RA and CWM backups, I've has issues with putting spaces in the names though so use _ or -
I have read around on the forums. I use Amon-ra and would like to rename some of my nand backups. I think the general advice is it will be fine as long as there is not any spaces in the name. If there is anything im missing before I do this.
Thanks.
mainstang said:
I have read around on the forums. I use Amon-ra and would like to rename some of my nand backups. I think the general advice is it will be fine as long as there is not any spaces in the name. If there is anything im missing before I do this.
Thanks.
Click to expand...
Click to collapse
go head sir!
As far as I know, spaces get converted to _ , so you should be fine either way.
your all set, here is what i name all my NAND's and everyone has showed up in Amon's
YYYY.MM.DD.ROMNAME.VERSION.THEME(if installed).Version(if different versions of themes/captured)
2011.02.14.WARM.RLS5.MB
today's date Warm RLS5 with matte blues theme
mainstang said:
I have read around on the forums. I use Amon-ra and would like to rename some of my nand backups. I think the general advice is it will be fine as long as there is not any spaces in the name. If there is anything im missing before I do this.
Thanks.
Click to expand...
Click to collapse
Not sure about amon, but i have clockwork, and I renamed my backups with the rom name after the date/time. When I went to restore them, I got a md5 mismatch error. I had to rename them back to what clockwork created to restore the backup. So just make sure you keep the date/time so if you need to, you can revert back to that.
sitlet said:
Not sure about amon, but i have clockwork, and I renamed my backups with the rom name after the date/time. When I went to restore them, I got a md5 mismatch error. I had to rename them back to what clockwork created to restore the backup. So just make sure you keep the date/time so if you need to, you can revert back to that.
Click to expand...
Click to collapse
Did you use an incorrect character, because I completely change mine, and no errors. A typical backup name for me might look like: CM7 build# xFeb
sitlet said:
Not sure about amon, but i have clockwork, and I renamed my backups with the rom name after the date/time. When I went to restore them, I got a md5 mismatch error. I had to rename them back to what clockwork created to restore the backup. So just make sure you keep the date/time so if you need to, you can revert back to that.
Click to expand...
Click to collapse
Only rename the folder, don't rename the files inside the folder.
Dude, just add a couple letters after the file. For example: if its a Fresh Rom you can just add xxxxxxFR at the end.
Sent from my PC36100 using XDA App
The last time I renamed my backups using Amon-ra, I was unable to restore in recovery. So, I just use a note app(ColorNote) to label my backups using the last 4 digits from the backup number. That way I know I won't have any issues.
I rename mine to what ever the date is and the ROM. Thats it. I use the dash symbol instead of the underscore cause for some reason it wouldnt recognize the underscores when I tried to restore. I also tried using dots instead of underscores and they wouldnt work for me either. I have found the only one that would work for me was the dash and Im on Amon Ra...
I rename my nands they look like this--> cm6wimaxalpha3 <-- or like -->cm7wimaxstockkernel <--
Without the arrows or dashes.
Sent from my WiMax infested cm7 Super...Mario...Saiyen...Street Fighter...oh yeah SuperSonic.gginggerbread!!!
I'm curious how renaming them works. I know i have to put it a certain way or it won't restore. So let's say I take my backup called
BDESW-20120204-2244 can I just rename it to Express by itself or no?
Sent from my PC36100 using XDA App
If you rename the folder, the md5's wont match, therefore it wont restore. I found this out the hard way before.
You can however just add text AFTER the folder name to indicate what rom backup it is. That way, when you want to restore it, just remove that text, leaving the original name. Just be sure the leave the original folder name intact.
sitlet said:
If you rename the folder, the md5's wont match, therefore it wont restore. I found this out the hard way before.
You can however just add text AFTER the folder name to indicate what rom backup it is. That way, when you want to restore it, just remove that text, leaving the original name. Just be sure the leave the original folder name intact.
Click to expand...
Click to collapse
well i found this post http://forum.xda-developers.com/showthread.php?t=1131784 so i added -express to the end of the name and about to see if it tries to restore
I rename mine all the time and no issues. Just do not add spaces that seems to screw it up.
What I do evo I just change 20120204-2222 to a rom that i am running, like cm7 ill put CM720204-2222. Never had any issues.
Sent from my PC36100 using Tapatalk
you can rename it to "turdburgler" if you want
I leave the letters, they tell what's backed up, and replace the numbers with a description.
I rename them so I know which backup it is.And before I started using firerat and was partitioned I made sure I put Sdext at the end.
Sent From My Evo 4G Amped Up On Verizon Tower Power!
i just guess then its a surprise oh hey im back on warm 2.2 lol
jk i usually dont keep that many back ups so im not much help other than for smartass comments
Renamed them and they restored fine
Sent from my PC36100 using XDA App
I leave the date portion so I know that it's the lastest backup I've done and just rename the number at the end for example nandroid backup BDESW-20120206-1274 I'll just rename it to let's say according to the Rom I'm using BDESW-20120206-MIUI
evo4gnoob said:
Renamed them and they restored fine
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I actually never rename, but thanks for asking the question, now I know too.
i didn't think that it would have any issues, since (at least with amon ra) the MD5 is inside the backup folder, with the *whatever*.img backup image
I am running Juggernaut v5.0 and recently did a backup. I wpied my phone and tried one of the ICS ports to see if i was happy with the build or wanted to wait for the official build (whenever that will be)...I ended up restoring my backup just fine. The following day i restored back to stock for some reason and when i rerooted my phone i tried to restore from the same backup and recieved "md5 mismatch"...i searched and found a few solutions to my problem and used this one http://forum.xda-developers.com/showthread.php?t=1606047 with no worries...i was just curious as to what would causes the mismatch in the first place as ive used it before to restore my phone?
sinfulgray said:
I am running Juggernaut v5.0 and recently did a backup. I wpied my phone and tried one of the ICS ports to see if i was happy with the build or wanted to wait for the official build (whenever that will be)...I ended up restoring my backup just fine. The following day i restored back to stock for some reason and when i rerooted my phone i tried to restore from the same backup and recieved "md5 mismatch"...i searched and found a few solutions to my problem and used this one http://forum.xda-developers.com/showthread.php?t=1606047 with no worries...i was just curious as to what would causes the mismatch in the first place as ive used it before to restore my phone?
Click to expand...
Click to collapse
it could be anything from changing or deleting folders/ files or any other "changes" that it was not there previously
You usually get those by changing the file name sometimes on some roms it's best to delete itto save space if you get it then redo it without naming it just have to remember the one it is lol
Sent from my SAMSUNG-SGH-T989 using xda premium
shankar10 said:
it could be anything from changing or deleting folders/ files or any other "changes" that it was not there previously
Click to expand...
Click to collapse
peppersu812 said:
You usually get those by changing the file name sometimes on some roms it's best to delete itto save space if you get it then redo it without naming it just have to remember the one it is lol
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I did change the file name so thats probably what did it then...i know some times i have to many backup and i dodnt know which one is which thanks
Hi all. I tried a new backup earlier then i tried a recover of said backup. No md5 match found when i chose that backup. Now i try a backup and no /sdcard also a no suitable error msg.. what happened it was running smothly.. i have clockwork touch. Should also note when i try to backup to external nothing happens in touch cwr..
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
You will need to be more specific when you say sdcard...the GS3 has an internal storage that is considered an SD card in android, as well as an external SD Micro slot beside the sim card. It sounds like maybe your internal storage has become corrupted possibly. Do you have a file explorer app? If so can you browse to /sdcard? Are there any files there? If there are and you can open them then it could just be a bad backup, if you cant then the storage is corrupt. If it is corrupted a format will fix you up at the exspense of losing whatever may be on it. If a format fails to correct the problem you likely have a defective device. Try accessing the internal sdcard manually and let us know what happens. As far as the external storage goes, unless you have installed an SD Micro in your phone nothing will happen when you try to backup to it as it is, in fact, empty.
Yes i can root explore to them both i have micrs sd also. Sorry for not clarifying. I could use to backup to external.. no more. Guess ill try and format thrm?? Sorry for typos using phone. I had my original backup on internal sd.. the stock. It became corrupt and when i backed up yesterday then factory wipe reset etc.. i tried to restore to the exact backup just made it replied no m5 match..
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Its so confusing all of them say 1970.. lol.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Weird now i root explore to clockworkmod backups and it has all 7 backups.. yesterday only 4 were there weird...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Ok just tried all 3 md5 mismatch.. restored back to current state and at the end i get a error msg saying cannot find /sdcard/ android-secure.img stop restore but then it restore complete maybe corrupt.. im afraid to format cause i have this backup on there working good.. lol. Guess ill try..
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Woah, easy there tiger....there is an edit button if you need to make changes to a post. Im sure the modderators are not going to be too happy with a quadruple post! :silly:
On to your issues, yes i have noticed with CMW recovery the dating system seems to be borked, atleast with the last 5.x version i used which does make deciding which file to restore from. The fact that you are getting MD5 mismatches seems to confirm the fact that your flash memory file system is corrupt, or possibly you have a bad recovery all together. If you can explore to the sd card you can copy the data off of it to a safer location while you determine the exact problem so as no to loose anything that could possibly be good. I would also recommend you download Clockwork Rom Manager from the market and install the latest recovery, 6. something or other. This may solve you problems all together.
P.S. - I got the error about android-secure.img every time i restorded (the error shows during the backup also if i recall) with CMW but it didnt seem to have any effect on the restore process
Yes i forgot to edit.my bad im on my phone. I uninstalled the cwm i had on phone redownloaded from playstore. Solved my date prob. So i must have downed a bad copy from a diff thread vs thr play store.. formatted both sd cards.. so lost tons but hey starting fresh aint so bad. With the premium cwm is touch included i could use free version.. thats what i did last time and had the isuue from manually install. Thanks for your help.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
You're welcome, glad to hear you got it sorted it out :good:. I have recently switched to TWRP recovery which seems to me to be a bit more reliable, although i have not used CWM's touch so i dont have any ground for comparison and this perception could simply be a placebo effect.