I NAND backed up my fresh Rom so I could get the PRI 1.40 update, and after the update I tried to restore back and when I click on my restore file I get the error something like " run nandroid-mobile.sh restore via adb"
I've backed up and restore plenty of roms, but for some reason this is the first error like this I've gotten.
I've been using and currently am using Amon RA 1.7 recovery.
I wiped/factory reset twice, data twice, and dalvic twice. Tried several times and even tried retoring another ROM from a few days ago and getting the same error.
I tried the command in adb, but that just doesn't seem right, I don't get a list of all my backup points, it just says "using a G1 keyboard, enter a directory name or substring and then <cr> to find matches or to accept defaults."
any help would be appreciated. Thanks!
first thing i would do is try a different recovery, RA 1.8 or clockwork. also, make sure that the md5 isnt corrupted. otherwise i would have no idea, i probably would just titanium my apps back and manually reset all my settings.
davebu said:
first thing i would do is try a different recovery, RA 1.8 or clockwork. also, make sure that the md5 isnt corrupted. otherwise i would have no idea, i probably would just titanium my apps back and manually reset all my settings.
Click to expand...
Click to collapse
I could do that, and I would, but I'd like to figure out the root cause of the problem so as not to have to do it in the future. I'd like to know I can Nand backup and Nand restore if and when I need to.
If I flash RA 1.8, i assume all my restore points show up the same?
Thanks
I've run into that problem for two different reason:
1. First, I had renamed my NAND backup files. I think if you place decimals within the file name (I.e "8.31.2010") it will give you that error
2. If you do not have a sufficient battery level it will not allow you to do a restore
astro004 said:
I've run into that problem for two different reason:
1. First, I had renamed my NAND backup files. I think if you place decimals within the file name (I.e "8.31.2010") it will give you that error
2. If you do not have a sufficient battery level it will not allow you to do a restore
Click to expand...
Click to collapse
I didn't rename the files, so that can't be it, but I just barely thought of the battery thing about 2 minutes ago. I actually got this error a couple days ago at night and gave up trying, the next morning (after charging the phone all night) I tried again, and it worked right off the bat.
I never thought it was because of the battery, but I do recall reading to make sure you have plenty battery left when flashing roms. I never knew that it was because it wouldn't physically let you flash. I thought it was more so your phone doesn't run out of juice while flashing.
I guess I'll try in the morning with a full battery and post back. I think I'm currently at 20% or so.
Thanks for the feedback.
Hello all
I find myself posting here because I don't have the required 10 posts to pose my question elsewhere.
I recently switched from Clockwork to AmonRA recovery. My second backup was of my stock SenseROM. My first backup was of CM 7.0.2.1, which could not be restored. My flash to CM 7.0.3.1 was successful, so I wasn't concerned.
Now, I cannot restore the stock SenseROM. I have transferred the recovery log to the SD card, but do not know how to decipher it.
I did change the name of the folder in /sdcard/nandroid, but not the names of the folders inside that folder.
Basically I'm not sure the proper way to rename a RA backup, and if there is any way to fix/repair the stock SenseROM that I cannot restore.
Thanks for your patience and help.
Skid
Skid71 said:
Hello all
I find myself posting here because I don't have the required 10 posts to pose my question elsewhere.
I recently switched from Clockwork to AmonRA recovery. My second backup was of my stock SenseROM. My first backup was of CM 7.0.2.1, which could not be restored. My flash to CM 7.0.3.1 was successful, so I wasn't concerned.
Now, I cannot restore the stock SenseROM. I have transferred the recovery log to the SD card, but do not know how to decipher it.
I did change the name of the folder in /sdcard/nandroid, but not the names of the folders inside that folder.
Basically I'm not sure the proper way to rename a RA backup, and if there is any way to fix/repair the stock SenseROM that I cannot restore.
Thanks for your patience and help.
Skid
Click to expand...
Click to collapse
I don't know the name it needs to be. But if you need stock rom Ruu sense to unroot I have links to the latest Ruu you would need in my guide.
Skid71 said:
Hello all
I find myself posting here because I don't have the required 10 posts to pose my question elsewhere.
I recently switched from Clockwork to AmonRA recovery. My second backup was of my stock SenseROM. My first backup was of CM 7.0.2.1, which could not be restored. My flash to CM 7.0.3.1 was successful, so I wasn't concerned.
Now, I cannot restore the stock SenseROM. I have transferred the recovery log to the SD card, but do not know how to decipher it.
I did change the name of the folder in /sdcard/nandroid, but not the names of the folders inside that folder.
Basically I'm not sure the proper way to rename a RA backup, and if there is any way to fix/repair the stock SenseROM that I cannot restore.
Thanks for your patience and help.
Skid
Click to expand...
Click to collapse
I was actually at a restaurant eating dinner when I was initially replying to your post and then all of a sudden, my phone rebooted and kept bootlooping so I had to rewipe and restore a nandroid backup while driving home...Sorry. Anyway, you cannot rename the folder which the nandroid backups are kept in, but you can rename the backups themselves as long as you don't use special characters. If you did change the name of the folder that the nandroids are in, you will not be able to restore. If you remember the name of the folder, change the name back to what it was. If you're familiar with ADB, connect your device to your computer, start the Terminal app (I use a MacBook) and then type, "adb connect". It *should* display the name of your device which is the same name as the folder that the nandroids are kept in.
Skid71 said:
Hello all
I find myself posting here because I don't have the required 10 posts to pose my question elsewhere.
I recently switched from Clockwork to AmonRA recovery. My second backup was of my stock SenseROM. My first backup was of CM 7.0.2.1, which could not be restored. My flash to CM 7.0.3.1 was successful, so I wasn't concerned.
Now, I cannot restore the stock SenseROM. I have transferred the recovery log to the SD card, but do not know how to decipher it.
I did change the name of the folder in /sdcard/nandroid, but not the names of the folders inside that folder.
Basically I'm not sure the proper way to rename a RA backup, and if there is any way to fix/repair the stock SenseROM that I cannot restore.
Thanks for your patience and help.
Skid
Click to expand...
Click to collapse
Just to be sure, the backup you're trying to restore is one that was created with Amon Ra, right? You can't restore a backup that was made with Clockwork. So, as long as the backup you're restoring was made by Amon Ra, it should restore.
You said you renamed the file right? Which folder exactly did you rename? If you renamed the nandroid backup itself, it cannot have any spaces in the name, or any odd characters. Keep the name simple, with no spaces. If that's what you renamed, try renaming it to something short and simple, then try restoring again.
If you renamed a different folder (the folder that the nandroid backups are actually in), I don't think you can do that at all. mine is like this : /nandroid/HT066HL***/(nandroid backups). If you renamed the one that is bolded, I'm almost positive that will bork things. You can only rename the backups themselves, and as I said, you can't use spaces. Double check your stuff, and see if it sounds like any of that might be your problem. Good luck.
EDIT: Dang Doug! Your post wasn't there when I started typing! I got distracted on a phone call during my reply, and delayed it way too long. Didn't mean to step on your toes man. At least our advice is the same! BTW, which rom bootlooped ya? I had that happen on decks 1.2m today.
k2buckley said:
Just to be sure, the backup you're trying to restore is one that was created with Amon Ra, right? You can't restore a backup that was made with Clockwork. So, as long as the backup you're restoring was made by Amon Ra, it should restore.
You said you renamed the file right? Which folder exactly did you rename? If you renamed the nandroid backup itself, it cannot have any spaces in the name, or any odd characters. Keep the name simple, with no spaces. If that's what you renamed, try renaming it to something short and simple, then try restoring again.
If you renamed a different folder (the folder that the nandroid backups are actually in), I don't think you can do that at all. mine is like this : /nandroid/HT066HL***/(nandroid backups). If you renamed the one that is bolded, I'm almost positive that will bork things. You can only rename the backups themselves, and as I said, you can't use spaces. Double check your stuff, and see if it sounds like any of that might be your problem. Good luck.
EDIT: Dang Doug! Your post wasn't there when I started typing! I got distracted on a phone call during my reply, and delayed it way too long. Didn't mean to step on your toes man. At least our advice is the same! BTW, which rom bootlooped ya? I had that happen on decks 1.2m today.
Click to expand...
Click to collapse
I'm thinking I borked myself then
I'll try to describe this...
nandroid/AmonRASenseROM/BDS-20110525-****
I should not have changed the bolded part, but instead, change the "BDS-20110525****" part?
I think I can change the name of that folder, or better yet, just move the "BDS..." folder to the folder that is named HT0CFH***** which contains my current CM 7.0.3.1 backup. I DID NOT change that folder name.
My gosh, did that make any sense?
And yes, that Sense ROM was backed up with AmonRA.
Really appreciate the help!
Skid71 said:
I'm thinking I borked myself then
I'll try to describe this...
nandroid/AmonRASenseROM/BDS-20110525-****
I should not have changed the bolded part, but instead, change the "BDS-20110525****" part?
I think I can change the name of that folder, or better yet, just move the "BDS..." folder to the folder that is named HT0CFH***** which contains my current CM 7.0.3.1 backup. I DID NOT change that folder name.
My gosh, did that make any sense?
And yes, that Sense ROM was backed up with AmonRA.
Really appreciate the help!
Click to expand...
Click to collapse
That is correct. You should not have changed the bolded part. You wanted to leave that what it originally was (I think it may be the phone's serial number, but not sure). The BDS-20110525 is the actual backup that you created. It is coded by the date you created the backup. So it looks like you created that one on the 25th (or 24th, often times the recovery will stamp my nandroid backup time as the next day for some reason. I'll make one on the 19th, but will have the date code of the 20th in there). So, as far as fixing the issue goes....I'm not positive how to get that folder named back to what it originally was..as I'm not sure what the exact name would have been. Hopefully someone else will chime in on it, and confirm what the name of that folder should be. I'll check in a second and see if that number is indeed my serial number. If it is, you should be able to rename it to that, and try it out.
Yes, I confirmed that the name of that folder should indeed be the serial number of your phone, in all capital letters. To get your serial number, you can either use adb, by typing 'adb devices', and the number it gives back to you will be your serial. If not, shut your phone down and pull your battery. Your serial number is back there. If you rename that folder with your serial number, you should be good to go (hopefully). Give it a shot.
Edit: And just to clarify, the one you CAN rename, is the BDS-20110525 one. Just be sure to not have any spaces in the name, or odd characters, as has already been noted. You should be on the right track after that.
k2buckley said:
That is correct. You should not have changed the bolded part. You wanted to leave that what it originally was (I think it may be the phone's serial number, but not sure). The BDS-20110525 is the actual backup that you created. It is coded by the date you created the backup. So it looks like you created that one on the 25th (or 24th, often times the recovery will stamp my nandroid backup time as the next day for some reason. I'll make one on the 19th, but will have the date code of the 20th in there). So, as far as fixing the issue goes....I'm not positive how to get that folder named back to what it originally was..as I'm not sure what the exact name would have been. Hopefully someone else will chime in on it, and confirm what the name of that folder should be. I'll check in a second and see if that number is indeed my serial number. If it is, you should be able to rename it to that, and try it out.
Click to expand...
Click to collapse
In trying to decipher the recovery log, I noticed that the other folder created in /nandroid was also the number of the phone (not sure if it's the serial). When I first made the Sense ROM backup, I changed the name of that folder (instead of the folder contained inside), then made a backup of the CM ROM. I noticed that it created another folder within /nandroid that was identical to the folder it created when I made the Sense backup. I hope I'm not confusing you as much as myself.
Anyway, what I did was rename the correct Sense ROM folder, then moved it to the "HT0CFHL****" folder. I hope that does the trick.
**Edit** I did use a - when renaming the Sense ROM. No spaces. That sound alright?
______________________________________________________________
Hope you don't mind another question while I'm here.
When performing a backup, should I just do a backup of the items that AmonRA recovery already has chosen, or should I do the Wimax, sd-ext, etc?
Would just like to make sure I'm doing this right.
Wish I would have started out with AmonRA instead of Clockwork (no offense meant)
Thanks again
Skid
Skid71 said:
In trying to decipher the recovery log, I noticed that the other folder created in /nandroid was also the number of the phone (not sure if it's the serial). When I first made the Sense ROM backup, I changed the name of that folder (instead of the folder contained inside), then made a backup of the CM ROM. I noticed that it created another folder within /nandroid that was identical to the folder it created when I made the Sense backup. I hope I'm not confusing you as much as myself.
Anyway, what I did was rename the correct Sense ROM folder, then moved it to the "HT0CFHL****" folder. I hope that does the trick.
______________________________________________________________
Hope you don't mind another question while I'm here.
When performing a backup, should I just do a backup of the items that AmonRA recovery already has chosen, or should I do the Wimax, sd-ext, etc?
Would just like to make sure I'm doing this right.
Wish I would have started out with AmonRA instead of Clockwork (no offense meant)
Thanks again
Skid
Click to expand...
Click to collapse
Okay, I am slightly confused, but not too confused, haha. So when you created the CM backup, and you say that you were left with a duplicate folder, which folder do you mean? That's all I'm confused about. Do you mean the one containing your serial number, that you renamed (the one that starts with H), or do you mean the BDS-2011...one? If you mean the BDS-2011 one, then that is normal. Every backup you create is automatically named BDS-20110524 (or whatever the date/time is). If you look closer, the time should be different. Anyways, if that is not what you're referring to, then it may have regenerated the folder which contains your backups (because it has to be named as your serial number, so since you changed the name of the first one, it may have regenerated a new one. In which case, if you moved your first backup to that new folder, it SHOULD work. (i think that's what you said you were doing..). If that worked, just delete the folder that you renamed, and leave the new one. You should then be good to go.
I hope I understood you right. If I did, it sounds like you should be set.
EDIT: forgot to answer your second question:
To be honest, I don't use Amon Ra 2.3. I have always stayed with the earlier version of 1.8.0, as it has NEVER faild me, so I saw no reason to change it. It is slightly different than the version you're on, as there are no backup options. It just automatically backs up what it needs to. With your version you do have the option to select what you backup. I for sure would make a couple backups that include your wimax.img. That is important to have, for if you ever lose your RSA keys, that backup of the wimax.img is how you would recover them. You would only need to include sd-ext if your sd card is partitioned, and you're using DT a2sd. If you are, then including the sd-ext is a must. If you don't have your card partitioned, or don't know what DT a2sd is, then you don't need to worry about backing up your sd-ext. I honestly don't recall what the other options are, and hopefully someone else who actively uses that recovery will help ya with that. I believe I remember there being an android_secure, recovery, or something like that. Sorry. Just definitely include the wimax.img. I believe that my friend Dougjamal posted something in the General section about the recommended way to backup using Amon Ra. Search that out, and you may find the answers. Good luck
Here's how I rename my nandroids and it works.
\nandroid\HT121HL07014\BDEARS-20110318-0300-koni_III
Anything else i Ever tried = fail
k2buckley said:
Okay, I am slightly confused, but not too confused, haha. So when you created the CM backup, and you say that you were left with a duplicate folder, which folder do you mean? That's all I'm confused about. Do you mean the one containing your serial number, that you renamed (the one that starts with H), or do you mean the BDS-2011...one? If you mean the BDS-2011 one, then that is normal. Every backup you create is automatically named BDS-20110524 (or whatever the date/time is). If you look closer, the time should be different. Anyways, if that is not what you're referring to, then it may have regenerated the folder which contains your backups (because it has to be named as your serial number, so since you changed the name of the first one, it may have regenerated a new one. In which case, if you moved your first backup to that new folder, it SHOULD work. (i think that's what you said you were doing..). If that worked, just delete the folder that you renamed, and leave the new one. You should then be good to go.
I hope I understood you right. If I did, it sounds like you should be set.
Click to expand...
Click to collapse
Yeah, confusing. But yes, you are correct sir. I'm itching to try flashing to it, but I'm a bit hesitant since the only current ROM backup I have is one with the pre-selected (in AmonRA) choices.
I'm not communicating very effectively tonight.
I appreciate the help.
Skid71 said:
Yeah, confusing. But yes, you are correct sir. I'm itching to try flashing to it, but I'm a bit hesitant since the only current ROM backup I have is one with the pre-selected (in AmonRA) choices.
I'm not communicating very effectively tonight.
I appreciate the help.
Click to expand...
Click to collapse
Well, I think you should be all set. If not, this is what I would do. Take both of your nandroid backups (the folder labeled BDS-2011....) and copy them to a different folder.
Then be sure you have a directory on your sd card named: nandroid/(your serial number). Then place both of your nandroid backups in that folder. (the one with your serial number). Then boot to recovery, and select backup/restore. Then select 'restore backup'. You should then see the folder named as your serial number. Select it. You should then see your backups. Select the one you want to restore, and try to do it. It should work.
k2buckley said:
EDIT: Dang Doug! Your post wasn't there when I started typing! I got distracted on a phone call during my reply, and delayed it way too long. Didn't mean to step on your toes man. At least our advice is the same! BTW, which rom bootlooped ya? I had that happen on decks 1.2m today.
Click to expand...
Click to collapse
(laughing)....You know it's not a big deal with me. As much as we post in these forums, it's a surety that we will post similar replies around the same time. As for the rom, it was SalvageMod. It hadn't happen prior to today and it haven't happened since. I was eating and replying from inside a Cracker Barrel restaurant when it occurred....lol
posting & replying via the XDA Premium app.
Just wanted to say thanks again to you both. I sincerely appreciate the time and help. Coming from WinMo 6.5, this is my first android device. It becomes quite the little hobby.
I hope to soak in knowledge like a sponge then pass it on.
XDA is a great community.
Thanks again
Skid
Skid71 said:
Just wanted to say thanks again to you both. I sincerely appreciate the time and help. Coming from WinMo 6.5, this is my first android device. It becomes quite the little hobby.
I hope to soak in knowledge like a sponge then pass it on.
XDA is a great community.
Thanks again
Skid
Click to expand...
Click to collapse
You're very welcome, my friend. Before purchasing my Droid Incredible last year, I was a die-hard Blackberry user. (First Blackberry was the 7290 and the last one was the original Bold 9000 with several other models in between). After I rooted the D-Inc, I realized that the capabilities with Android devices were vast. I then wanted a larger screen and was torn between the Droid X and the EVO. Being that I was already familiar with HTC Sense, I chose the EVO and without doubt, I made the right choice. This device is amazing and through trial and error and from being helped by the good people who frequent these forums, I've learned a great deal and am still learning. I love this community and I try to help others and often as I can. The success rate is less than 100% but the effort is more than that....lol. Anyway, take care and enjoy your day...
posting & replying via the XDA Premium app.
Exact same thing happened to me. I kept reading posts saying to get amon recovery. So I did. But when I went to try and restore it wouldn't let me choose a clockwork restore. I just used Rom manager and re flashed clockwork. Then went and did a restore. I like clockwork so I will keep it. Don't know what makes amon so special. Seems like the same options.
Sent from my PC36100 using XDA App
sand1303 said:
Exact same thing happened to me. I kept reading posts saying to get amon recovery. So I did. But when I went to try and restore it wouldn't let me choose a clockwork restore. I just used Rom manager and re flashed clockwork. Then went and did a restore. I like clockwork so I will keep it. Don't know what makes amon so special. Seems like the same options.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Amon Ra is known to be more reliable. It wipes better, and flashes more reliably. Clockwork works flawlessly for some, but not for all. Amon Ra seems to be nearly flawless for all who use it. Also, if you continue using clockwork, you will surely run into some zips that you cannot flash, such as anything that is scripted with edify. Clockwork only supports amend scripting, and there are still PLENTY of zips out there that are edify only. In that case, clockwork will tell you that it can't flash it, and you need to change the scripting to amend. Amon flashes both amend and edify. Also, the newest clockwork doesn't flash radios for some reason, the flash will just not take.
So yea, clockwork works perfectly, and everyone else who suggests amon ra is wrong.
k2buckley said:
So yea, clockwork works perfectly, and everyone else who suggests amon ra is wrong.
Click to expand...
Click to collapse
Wow, I never said it was perfect or anyone was wrong. I simply never ran into problems with clockwork and had a problem with amon. So I didn't know why people would use it.
I greatly appreciate you informing me. I guess if I ever have a problem with clockwork and decide to use amon I will do a backup first thing so restore will be usable.
I also saw on Rom manager that certain things wouldn't work without clockwork. And Rom manager seems to make flashing easier.
Sent from my PC36100 using XDA App
sand1303 said:
Wow, I never said it was perfect or anyone was wrong. I simply never ran into problems with clockwork and had a problem with amon. So I didn't know why people would use it.
I greatly appreciate you informing me. I guess if I ever have a problem with clockwork and decide to use amon I will do a backup first thing so restore will be usable.
I also saw on Rom manager that certain things wouldn't work without clockwork. And Rom manager seems to make flashing easier.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yea, sorry didn't mean to come off harsh. Sorry about that. And yes, Amon Ra doesn't work with rom manager. I won't get started on my opinions on ROM manager, lol
Clockwork jacked up my phone before and left a bad taste in my mouth!
It's all good!
Sent from my PC36100 using XDA App
i would love to create a nandroid backup for my galaxy s 3 (sgh-t999)... but i keep getting these error messages when i am doing the backup through cwm
"unable to find volume."
"Error finding an appropriate backup handler."
does anybody know how to fix this? i know that this is not something that will impede my daily use of the phone but since i flash roms, it is a great idea to have a backup just in case.
does anybody have any ideas on how to fix this... or has anybody dealt with this before?
Having the same issue on my AT&T
have you tried other versions (even older) of clockwork? There were issues like this for Sprint, going back to 5.8.4.5, eve though v 5.8.4.8 was available, did the fix. try that
hes right, went to rom manager and looked at available recoveries at the bottom and picked the oldest one available which was .5 and now i can make backups, and have access to the external sd, yay
Good deal... Click thanks....
Sent from my SPH-L710 using xda premium
Naddict said:
have you tried other versions (even older) of clockwork? There were issues like this for Sprint, going back to 5.8.4.5, eve though v 5.8.4.8 was available, did the fix. try that
Click to expand...
Click to collapse
thanks for the suggestion... i tried that. there were two older versions. the one that was .5 wasnt even able to mount the sd card. the .6 version had the same issue as the latest version.
also... might mean nothing... but i noticed that when it tries to do a backup, i dont see cwm scrolling through all of the files like it is backing up like it did with all my other phones. it says backing up data, but it doesnt like go through file by file. is that normal?
SOLVED!!!
found a post where it solved my problem... hope it works for everybody else. just deleting the ".android_secure" folder on my sd card solved everything.... its always the easiest solutions that seem to evade us. if it helps, you should thank the person who solved it
http://forum.xda-developers.com/showpost.php?p=21292655&postcount=42