Safestrap backups not appearing in SafeStrap Recovery on second phone. - RAZR HD Q&A, Help & Troubleshooting

I have been banging my head against the wall here..
I am trying to backup a phone that is going back to verizon and restore it to the new one they cross-shipped me (Same model).
When I go into Safestrap recover, the backup just isn't there!
What the heck, I've never had this problem with SS on my OG Razr MAXX.

Just create a backup using nanodroid
Sent from my PACMAN MATRIX HD MAXX

abuttino said:
I have been banging my head against the wall here..
I am trying to backup a phone that is going back to verizon and restore it to the new one they cross-shipped me (Same model).
When I go into Safestrap recover, the backup just isn't there!
What the heck, I've never had this problem with SS on my OG Razr MAXX.
Click to expand...
Click to collapse
Make a new backup. Be sure to name the backup.
Once the back up finishes reboot into the OS.
Use your file explorer to navigate to the TWRP folder.
Then go to BACKUPS. In BACKUPS there should be two folders. These folders have names with random letters and numbers. EX: TA26905GDQ.
The two sub-folders contain each backup. Look in both and find the old one.
Once you have found the old one, the one you want to restore, move it to the folder with the new back up.
Reboot to recovery and the old backup should be there for you to restore.
Enjoy...

Related

[Q] Nandroid backups

I've just taken the plunge and installed my first custom ROM (Infin1ty, definitely worth a look) and took a Nandroid backup of my stock image.
Is there any way for me to check that the nandroid backup will work before I use it?
If not, as a last resort, could I flash the full 2.3.4 update? I have a i9023.
From other threads I have seen, it appears that I can copy any backups I have to my PC and they should be OK as long as I don't put spaces in the names.
Try this
Try the app, Android File Verifier. I can't post a link since I'm new to XDA.
Once you have it installed.
Press, Select File, ClockworkMod, backup, the date of your nandroid backup, long press on nandroid.md5 and choose "Verify nandroid backup" from the menu that pops up.
Graham19 said:
I've just taken the plunge and installed my first custom ROM (Infin1ty, definitely worth a look) and took a Nandroid backup of my stock image.
Is there any way for me to check that the nandroid backup will work before I use it?
If not, as a last resort, could I flash the full 2.3.4 update? I have a i9023.
From other threads I have seen, it appears that I can copy any backups I have to my PC and they should be OK as long as I don't put spaces in the names.
Click to expand...
Click to collapse
Just restore it to test. If it works, great! If it doesn't post again and we'll help you out

Newly rooted. Backup question

I'm no noobie to being a super user. Usually after rooting a device I would back up to be safe, then flash a Rom and eventually delete the stock backup. Simply because I'm happy to see it gone. My question is, since I really like the stock one s boot animation and image, will restoring my stock backup restore these files? Or do I need to back them up? If so how. Never needed to.:what:
Sent from my HTC One S using XDA
Animations at least are in /system/customize/resource/ files are named up- and downanimation or similar. These should be restored automatically when restoring from a nandroid backup. Check threads about this in Apps and themes section

[Recovery] [official] Clockworkmod Touch 6.0.1.0 flash able zip

I put the latest touch recovery from clockworkmod into a flashable zip.
It works with ICS. It is the same recovery as the one you would have to pay for to install with ROM manager.
TO INSTALL CWM TOUCH RECOVERY........
Flash this in recovery as you would any ROM or mod.
Here is the link:
http://db.tt/Ud9qVq7V
I found the recovery http://www.clockworkmod.com/rommanager
**** This is different than sk8tr's version btw. His has a custom ui and this is CWM official. ****
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
If anyone is wondering this doesn't look like its a disaster just as 5.8.4.3 was. I flashed miui and it booted up fine but if anyone has any issues please share.
Sent from my SGH-I727 using xda premium
Working good on my Hercules just flashed aokp jb and aint need any superwipe scripts either
thank you, works great!
Updated op to avoid confusion.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Thanks for the info!
sent from a device using an app
Okay, so I ran a backup and restore test on cm9 and cm10. I thought it was sk8t's version causing me problems restoring backups but the issue is similar on this build.
The backup file that gets created doesn't contain all the data for a full restore -- much of it gets stored in the "blobs" folder in cwm (someone more knowledgeable than me can probably explain better). Also, it takes a REALLY long time to create a backup.
Using the standard restore doesn't work on (on this or on sk8t's version). I keep getting "error restoring system" message and it won't restore. I tried to do an advanced restore doing each part individually but that didn't work either.
Restoring an old rom from before they changed the backup method works fine though. I haven't tried restoring using ROM Manager yet but I may try that next--I'm thinking that's what the new system is designed for...
EDIT: Rom manager fails too. Same error restoring system message.
Please post here if you can successfuly backup and restore cm9 or cm10 (or any other roms) so we can figure out if its just me
skrambled said:
Okay, so I ran a backup and restore test on cm9 and cm10. I thought it was sk8t's version causing me problems restoring backups but the issue is similar on this build.
The backup file that gets created doesn't contain all the data for a full restore -- much of it gets stored in the "blobs" folder in cwm (someone more knowledgeable than me can probably explain better). Also, it takes a REALLY long time to create a backup.
Using the standard restore doesn't work on (on this or on sk8t's version). I keep getting "error restoring system" message and it won't restore. I tried to do an advanced restore doing each part individually but that didn't work either.
Restoring an old rom from before they changed the backup method works fine though. I haven't tried restoring using ROM Manager yet but I may try that next--I'm thinking that's what the new system is designed for...
EDIT: Rom manager fails too. Same error restoring system message.
Please post here if you can successfuly backup and restore cm9 or cm10 (or any other roms) so we can figure out if its just me
Click to expand...
Click to collapse
Did a backup on CM10 Alpha 1. It took awhile but didn't seem to take any longer than a CM 5.x backup. Modified a few things, updated a couple apps, and then did another backup - went a bit quicker. Doing a restore now but it's past the restoring system portion so I'm assuming it'll all be good. I'll edit this if it craps out at some point.
As for the blobs, this is new to CM6.x and from what I understand is supposed to make backups a little quicker and use less space as it will only backup what's been changed since a previous backup instead of the entire thing like CM5.x. Not sure at all on all the technical details but I'd suspect the blobs contain what's been changed at the point of backup and each backup "container" file indicate which blobs to restore...
EDIT: Restore completed just fine.
so you're saying that if I have a backup stored and create a new back up it only backs up the changes since the last one? If so, that sucks. I always like to keep a solid backup and then after numerous changes back up again and delete the old one. Looks like it's back to old faithful 5.8.1.3 for me.
(UPDATE) confirmed. My new backup was 20MB.
Honestly i prefer twrp recovery.. just wanted to provide this for those that needed it.
But, since TWRP does an UNCOMPRESSED backup i can have a nandroid backup done in a little over 2 minutes. Same for restore.. very fast.
TWRP can be set to compress the backup.. but i prefer speed over less space.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
copene said:
so you're saying that if I have a backup stored and create a new back up it only backs up the changes since the last one? If so, that sucks. I always like to keep a solid backup and then after numerous changes back up again and delete the old one. Looks like it's back to old faithful 5.8.1.3 for me.
(UPDATE) confirmed. My new backup was 20MB.
Click to expand...
Click to collapse
Here's the explanation of how it works:
https://plus.google.com/u/0/103583939320326217147/posts/L5aVZe7C9vg
pixelens said:
Here's the explanation of how it works:
https://plus.google.com/u/0/103583939320326217147/posts/L5aVZe7C9vg
Click to expand...
Click to collapse
Thanks. There should be a "FULL backup" and "BLOB backup" option. I'm rolling with 5.8.1.3 cause it's never fu**ed me over (yet).
copene said:
Thanks. There should be a "FULL backup" and "BLOB backup" option. I'm rolling with 5.8.1.3 cause it's never fu**ed me over (yet).
Click to expand...
Click to collapse
I'm not sure if I follow what the point would be? I thought the same, but after reading that and doing a few tests, I'm confident this will do just as well - if not better.
Might be worth mentioning/requesting from Koushik Dutta depending on your reasoning or need.
I think I figured out what the problem was for me in not getting backups to restore (but someone please post if you disagree). I was getting an "Error while restoring /system!" message every time.
Every time I make a backup I go into Root Explorer and change the backup name so that I know which rom it is. Today I did a backup and didn't change the backup name and I was able to restore it successfully.
Changing the name of yesterday's backup to it's original name, however, did not fix the problem. Those backups still won't restore.
skrambled said:
I think I figured out what the problem was for me in not getting backups to restore (but someone please post if you disagree). I was getting an "Error while restoring /system!" message every time.
Every time I make a backup I go into Root Explorer and change the backup name so that I know which rom it is. Today I did a backup and didn't change the backup name and I was able to restore it successfully.
Changing the name of yesterday's backup to it's original name, however, did not fix the problem. Those backups still won't restore.
Click to expand...
Click to collapse
I've always changed the name of my backup folder to make it more descriptive. One thing I read along time ago was that it only works if you don't include any spaces in the changed folder name. And I've never had any problems with restoring any of them. However, if you indeed did not include any spaces, then maybe it's been changed in CWM 6.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
plwalsh88 said:
I've always changed the name of my backup folder to make it more descriptive. One thing I read along time ago was that it only works if you don't include any spaces in the changed folder name. And I've never had any problems with restoring any of them. However, if you indeed did not include any spaces, then maybe it's been changed in CWM 6.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Didn't add any spaces. I only added cm9 or cm10 to the end of the file name (that's how I know I changed it back to the original names when I tried to restore yesterday's backups).
skrambled said:
Didn't add any spaces. I only added cm9 or cm10 to the end of the file name (that's how I know I changed it back to the original names when I tried to restore yesterday's backups).
Click to expand...
Click to collapse
Gotcha. That's interesting then; don't know what it could be.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Hey majic I got a suggestion to cut down on confusion. Put official in the title. At first I thought sk8 had to threads. I thank you kind sir for zipping and uploading this official version. You da man....
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
skrambled said:
Didn't add any spaces. I only added cm9 or cm10 to the end of the file name (that's how I know I changed it back to the original names when I tried to restore yesterday's backups).
Click to expand...
Click to collapse
never had issues changing names of back up folders, what did you use to change the folder name , you could have a space at the end of the file name and dont even know it, use backspace to delete it, if u know dos try its naming conventions
sorry but how is this recovery different from sk8's recovery? That one's also CWM Touch 6.0.1.0 and also flashable zip ... ?
Thanks!

[Q] Error while restoring nandroid of old GS3 to new replacement GS3

I got a replacement GS3 from Verizon because my current one had a charge port issue. I rooted and am using CWM 6.0.2.3 and get "error while restoring /system" when I try tp restore the nandroid of my old phone to the new one. How do I fix this?
Did you change the name of the nandroid at all? It's also possible that the backup you made contained individual phone information specific to your old phone...I seem to remember a thread before that mentioned it wasn't a good idea to move a nandroid to a new Samsung phone.
Edit: I found the thread shortly after hitting submit - http://forum.xda-developers.com/showthread.php?t=1795031
laurasaurisrex said:
Did you change the name of the nandroid at all? It's also possible that the backup you made contained individual phone information specific to your old phone...I seem to remember a thread before that mentioned it wasn't a good idea to move a nandroid to a new Samsung phone.
Click to expand...
Click to collapse
No I didnt't change anything. Anyway I can fix this?
laurasaurisrex said:
Did you change the name of the nandroid at all? It's also possible that the backup you made contained individual phone information specific to your old phone...I seem to remember a thread before that mentioned it wasn't a good idea to move a nandroid to a new Samsung phone.
Edit: I found the thread shortly after hitting submit - http://forum.xda-developers.com/showthread.php?t=1795031
Click to expand...
Click to collapse
If anyone has a way I can workaround that, please help! I don't want to setup my phone all over again!
droxide said:
If anyone has a way I can workaround that, please help! I don't want to setup my phone all over again!
Click to expand...
Click to collapse
there are a couple of apps where you can just extract the nandroid apps on the play store, but if you want the full restore, the file is probably corrupted.
dragon1357 said:
there are a couple of apps where you can just extract the nandroid apps on the play store, but if you want the full restore, the file is probably corrupted.
Click to expand...
Click to collapse
Yeah I used to use titanium backup but my phone is very customized, CM10, diff kernel, and a very highly customized home screen so I'd rather restore the nandroid if there is some kind of workaround. I also want all my data, texts, etc. without using titanium backup. When I used ti backup in the past, I had a bunch of different issues restoring apps and data, force closes, etc.
http://forum.xda-developers.com/showthread.php?t=1949020
I followed the directions in the last post of that thread.. I made a backup of the new phone, moved the old nandroid from old phone to the twrp back up folder in my new phone. I copied the new backup name and deleted the new backup. i pasted the name into the old back up, I tried to restore and i get an error "no partitions selected for restore. Is it because Im using twrp and I made the old backup with CWM?
Someone help!
droxide said:
http://forum.xda-developers.com/showthread.php?t=1949020
I followed the directions in the last post of that thread.. I made a backup of the new phone, moved the old nandroid from old phone to the twrp back up folder in my new phone. I copied the new backup name and deleted the new backup. i pasted the name into the old back up, I tried to restore and i get an error "no partitions selected for restore. Is it because Im using twrp and I made the old backup with CWM?
Someone help!
Click to expand...
Click to collapse
That could be it. They back up with different formats. Cwm uses the blob folder twrp does not.
Sent from my SCH-I605 (AKA NOTE 2)
kintwofan said:
That could be it. They back up with different formats. Cwm uses the blob folder twrp does not.
Sent from my SCH-I605 (AKA NOTE 2)
Click to expand...
Click to collapse
Ok so how can I switch from TWRP to CWM without resetting everything?
droxide said:
Ok so how can I switch from TWRP to CWM without resetting everything?
Click to expand...
Click to collapse
Ya, you should be able to flash it through odin no problem
Sent from my SCH-I535
droxide said:
Ok so how can I switch from TWRP to CWM without resetting everything?
Click to expand...
Click to collapse
You can just use ez recovery from the play store
Sent from my SCH-I605 (AKA NOTE 2)

[Q] Newer CWM, md5 mismatch won't allow recovery.

I don't know if it has to do with having installed a newer version of ClockworkMod Recovery (6.0.3.1), but when I go to restore a previous backup, I get "md5 mismatch!" and no recovery is done.
Things that my non-developer brain can think of that might be relevant:
I may have changed the name of the folder for the recovery (I didn't think this mattered)
I am trying to go from CyanogenMod M5 to a recovery of an M2 (don't think this should matter).
The recovery was made using a previous version of ClockworkMod Recovery (an earlier, but 2013, version)
The recovery folder was stored on my computer and I put it on my phone using USB on-the-go (I have tried this twice to make sure one wasn't corrupted or whatever).
Thanks for any pointers. Do have have to install an older version of ClockworkMod Recovery or is there something simpler I could do? Thanks! :good:
LudicrousPeed said:
I don't know if it has to do with having installed a newer version of ClockworkMod Recovery (6.0.3.1), but when I go to restore a previous backup, I get "md5 mismatch!" and no recovery is done.
Things that my non-developer brain can think of that might be relevant:
I may have changed the name of the folder for the recovery (I didn't think this mattered)
I am trying to go from CyanogenMod M5 to a recovery of an M2 (don't think this should matter).
The recovery was made using a previous version of ClockworkMod Recovery (an earlier, but 2013, version)
The recovery folder was stored on my computer and I put it on my phone using USB on-the-go (I have tried this twice to make sure one wasn't corrupted or whatever).
Thanks for any pointers. Do have have to install an older version of ClockworkMod Recovery or is there something simpler I could do? Thanks! :good:
Click to expand...
Click to collapse
Changing the name for CWM backups will cause md5 mismatches. If you did this, you should switch and use TWRP which allows native nandroid renaming. Delete your CWM backups and stick to TWRP. It could also be an issue between CWM backups over different CWM versions however if you renamed your backups and each of those renamed backups failed except the ones you left alone then you found your issue.
SlimSnoopOS said:
Changing the name for CWM backups will cause md5 mismatches. If you did this, you should switch and use TWRP which allows native nandroid renaming. Delete your CWM backups and stick to TWRP. It could also be an issue between CWM backups over different CWM versions however if you renamed your backups and each of those renamed backups failed except the ones you left alone then you found your issue.
Click to expand...
Click to collapse
Thanks for the insight. Seems like I should just be able to change the folder name back to what it was named by default, if I can make sure it is correct. Do you think that's worth trying or is it deeper than that? I'll use TWRP from now on since it seems to be more robust (CWM was just the recommended recovery from Cyanogenmod)
LudicrousPeed said:
Thanks for the insight. Seems like I should just be able to change the folder name back to what it was named by default, if I can make sure it is correct. Do you think that's worth trying or is it deeper than that? I'll use TWRP from now on since it seems to be more robust (CWM was just the recommended recovery from Cyanogenmod)
Click to expand...
Click to collapse
Depends on how much you value those nandroids. I only keep two on my phone so it's no thing for me to delete my backups entirely. You can rename them to their original names and your issue should go away.
Sent from my SCH-I535 using Tapatalk 4 Beta
Make sure the name of the backup folder doesn't have any spaces. When I renamed backups and had a space in the name I would get that same "md5 mismatch!" error.
Thanks! So renaming the backup to what it was originally allowed the backup to attempt to restore, but data could not be restored. Attempting to boot it resulted in nor getting past the boot animation. I wonder if it was because I didn't have enough space left on my phone or of it had to so with the newer firmware I installed. Or something else.
Slightly of topic at this point but not really. Any ideas why data could not be restored?
Sent from my SCH-I535 using Tapatalk 2
LudicrousPeed said:
Thanks! So renaming the backup to what it was originally allowed the backup to attempt to restore, but data could not be restored. Attempting to boot it resulted in nor getting past the boot animation. I wonder if it was because I didn't have enough space left on my phone or of it had to so with the newer firmware I installed. Or something else.
Slightly of topic at this point but not really. Any ideas why data could not be restored?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I had a similar issue about a year ago. I resolved it by generating a new md5, but I don't recall what method I used. Do a search for that.

Categories

Resources