i did a nandroid backup and tried restoring it, and it gets stuck at the bootscreen.
any ideas?
Did you wipe before restoring?
yup, complete wipe
come on guys. when i do the restore on kingklicks 2.1 it loops the nexus one bootscreen
smjfosho said:
come on guys. when i do the restore on kingklicks 2.1 it loops the nexus one bootscreen
Click to expand...
Click to collapse
I want to preface this by saying it is a guess.
Theory 1
Since the rom had written data to the EXT partition, when you wiped before restoring, it is looking for something on that partition???? You may need to start over with Kingklick. If you use Bart or Switchrom to do your backups, you should always be able to restore without need ing to wipe.
Theory 2
After you wipe (everything) make sure you "repair ext" from the recovery menu.
i did a BART backup and restore and that worked perfect
Related
ok so i was getting ready to flash newvision v3 by jac and drizzy...so i went to bootloader....wiped my ext3 and then wiped my phone... then i did a nandroid backup and I flashed... then restored it...after that its on the g1 screen and i havent tried recovery yet and i just realized that since i wiped before nandroid it didnt really backup anything...what should i do???just reflash if recovery works???
Noobyflasher said:
ok so i was getting ready to flash newvision v3 by jac and drizzy...so i went to bootloader....wiped my ext3 and then wiped my phone... then i did a nandroid backup and I flashed... then restored it...after that its on the g1 screen and i havent tried recovery yet and i just realized that since i wiped before nandroid it didnt really backup anything...what should i do???just reflash if recovery works???
Click to expand...
Click to collapse
Yeah, you confused your steps a little. Seeing that you did a nandroid after all of the wiping, you essentially just made a backup of your boot, data, recovery, and system images but your cache image is not gonna contain much because you wiped I'm pretty sure. If you flashed your new ROM, you can't flash your nandroid backup as that will take you back to your old ROM. Nandroid isn't a back up tool in the way you want to you use (settings, preferences etc) It is a tool that will restore your system in case you mess something up. If you want the new drizzy JAC build, you just flash that and leave your nandroid for a rainy day or if you screw up a flash and get a bootloop.
I have been browsing google for an answer to this problem but nothing I have found has seemed to help, so I suppose I'll ask and see if anyone else has had this problem had knows what to do.
I try to run a nandroid backup from cyanogen's recovery, it simply keeps making dots and will easily fill up a screen.
Furthermore, i try and do a "nandroid-mobile.sh -b" and it hangs on the data.img part for in excess of 20 minutes.
Any ideas what I can try to get nandroid to work again? It has failed to work both on the last version of SuperD and on the newest which I updated last night (1.11?)
I suppose I could try a full wipe and reinstall, but I haven't donated for the full Titanium backup yet... and restoring is a pain until I do that.
Is there anything besides a wipe that I could try?
Thanks
Tylerspilker said:
I have been browsing google for an answer to this problem but nothing I have found has seemed to help, so I suppose I'll ask and see if anyone else has had this problem had knows what to do.
I try to run a nandroid backup from cyanogen's recovery, it simply keeps making dots and will easily fill up a screen.
Furthermore, i try and do a "nandroid-mobile.sh -b" and it hangs on the data.img part for in excess of 20 minutes.
Any ideas what I can try to get nandroid to work again? It has failed to work both on the last version of SuperD and on the newest which I updated last night (1.11?)
I suppose I could try a full wipe and reinstall, but I haven't donated for the full Titanium backup yet... and restoring is a pain until I do that.
Is there anything besides a wipe that I could try?
Thanks
Click to expand...
Click to collapse
I have the same issue using Amon Ra's recovery with Nandroid.
I end up pulling the battery and rebooting.
Take a look in your Nandroid backup folder on your SD card....you will see files that are several GB in size.
The nandroid appears to get stuck in a loop.
I have not had a successful nandroid backup made since CM-Recovery. I might go back to it but Amon Ra has a lot more stuff.
I reverted over to Amon Ra recovery from the JF+ Cyan one, and did a full wipe and restore of everything and nandroid was working well after.
Not sure what happened, but its all peachy now. I donated to Titanium backup, and it is the best app I have used... makes me want to switch Roms daily now!
Tylerspilker said:
I reverted over to Amon Ra recovery from the JF+ Cyan one, and did a full wipe and restore of everything and nandroid was working well after.
Not sure what happened, but its all peachy now. I donated to Titanium backup, and it is the best app I have used... makes me want to switch Roms daily now!
Click to expand...
Click to collapse
Which Amon_Ra? I had the same issue on 1.5.x and 1.6.2.
Still no joy on nandroid or BART.
Hey guys,
I've been using nandroid since my magic days. With my magic, I've had no problems whatsoever always wiping and doing a restore of my old nandroid backups. However, it does not seem to be the case with my captivate for some reasons.
Here are a few methods I've tried:
1) Factory wipe/data reset using clockwork recovery and restore nandroid (which I did with my magic.. not sure why they don't work)
2) Flash to 2.1 stock and do nandroid restore.
3) Flash to the ROM after a wipe that I want to restore to then do nandroid restore.
All three methods allow me to complete nandroid restore but upon reboot it's just non-stop FC city.
Can anyone guide me? Thank you
Nothing to see here, move along.
Thanks bud you are sooo helpful.
Sent from my SAMSUNG-SGH-I897
koreancanuck said:
Hey guys,
I've been using nandroid since my magic days. With my magic, I've had no problems whatsoever always wiping and doing a restore of my old nandroid backups. However, it does not seem to be the case with my captivate for some reasons.
Here are a few methods I've tried:
1) Factory wipe/data reset using clockwork recovery and restore nandroid (which I did with my magic.. not sure why they don't work)
2) Flash to 2.1 stock and do nandroid restore.
3) Flash to the ROM after a wipe that I want to restore to then do nandroid restore.
All three methods allow me to complete nandroid restore but upon reboot it's just non-stop FC city.
Can anyone guide me?
I am not sure but do you only have one backup you are trying to use? Could be an issue with backup. Is three any lag fix in the equation? It sucks but if three worst of it is you can flash the rom but not restore your apps then I guess consider your self lucky
Captivate
Cog 2.4
Click to expand...
Click to collapse
Yep. I disable my lagfixes before doing restores. To be honest it's not that big of a hassle since I can just use tibu pro and do one click restore for apps and restore my settings as well. And nandroid takes so much longer on captivate than magic D: Still it would be nice to always go back..
Sent from my SAMSUNG-SGH-I897
when i go into recovery mode, and select backup / restore, should i be selecting backup "data" or backup "all"? what is the difference?
I believe backup data will just backup your user apps and basic data on sd. Backup all baghdad up system apps and data as well. Significance is that you would not want to restore all if you were not running the same rom
mcord11758 said:
I believe backup data will just backup your user apps and basic data on sd. Backup all baghdad up system apps and data as well. Significance is that you would not want to restore all if you were not running the same rom
Click to expand...
Click to collapse
So if i would like to restore my phone to the state it is in now, would i be doing a backup "Data" or backup "all"?
when i go into recovery -->backup/restore --> backup, it says backup and restore data is recommended, and that backup and restore all was "use at own risk" or something along that line.
If you are looking to restore your current state on rom "x" down the line, our if you are playing with themes and something goes wrong you would restore all. To be honest I am not sure why you would ever restore just data, that is why I use titanium backup.
You would not want to restore a backup from rom x onto rom y
I only do nandroid backups if I am planning on playing with themes
mcord11758 said:
If you are looking to restore your current state on rom "x" down the line, our if you are playing with themes and something goes wrong you would restore all. To be honest I am not sure why you would ever restore just data, that is why I use titanium backup.
You would not want to restore a backup from rom x onto rom y
I only do nandroid backups if I am planning on playing with themes
Click to expand...
Click to collapse
hmm. so I shouldnt be using nandroid backup/restore to get back to where i originally was if i was testing out a different rom?
I think you have me backwards
If you are running phoenix rom, but wanted to try paragon, you could do a nandroid backup of phoenix so that your set up on that rom is saved. Try paragon, but maybe it uss not for you, so you go back to phoenix. now you can restore your nandroid after you reflashed phoenix to get your settings and apps back. You can not restore the phoenix backup while on paragon. Well actually you could but it will likely cause issues
Now if you wanted to play with themes and you try one out and tower phone won't boot. You can go back to recovery and restore to get rid of the theme
mcord11758 said:
I think you have me backwards
If you are running phoenix rom, but wanted to try paragon, you could do a nandroid backup of phoenix so that your set up on that rom is saved. Try paragon, but maybe it uss not for you, so you go back to phoenix. now you can restore your nandroid after you reflashed phoenix to get your settings and apps back. You can not restore the phoenix backup while on paragon. Well actually you could but it will likely cause issues
Now if you wanted to play with themes and you try one out and tower phone won't boot. You can go back to recovery and restore to get rid of the theme
Click to expand...
Click to collapse
So that means i should always "reflash" back to phoenix rom before restoring my backup onto phoenix?
in this case, would i be using the "restore/backup data" or the "restore/backup all" from the recovery menu? like i said earlier, there is a recommendation in the menu to use backup/restore data and a warning with backup/restore all.
dsu said:
So that means i should always "reflash" back to phoenix rom before restoring my backup onto phoenix?
in this case, would i be using the "restore/backup data" or the "restore/backup all" from the recovery menu? like i said earlier, there is a recommendation in the menu to use backup/restore data and a warning with backup/restore all.
Click to expand...
Click to collapse
Yes you would reflash phoenix
Backup all, I believe the warning is to prevent you from restoring all from one rom to another.
Ok, I have a backup from stock 2.1. I am running paragon which is 2.2.1. If I try to restore my stock backup I will likely get stock in a boot loop and will have to use odin to recover. I believe, note believe, that if I restored just data I would be ok because I would not be restoring any system information. I use titanium to back up my apps, so I do not see a use for the option
mcord11758 said:
Yes you would reflash phoenix
Backup all, I believe the warning is to prevent you from restoring all from one rom to another.
Ok, I have a backup from stock 2.1. I am running paragon which is 2.2.1. If I try to restore my stock backup I will likely get stock in a boot loop and will have to use odin to recover. I believe, note believe, that if I restored just data I would be ok because I would not be restoring any system information. I use titanium to back up my apps, so I do not see a use for the option
Click to expand...
Click to collapse
I see, still a bit confused because because i have a stock backup 2.2 from "rom manager". When switching between roms before, i would restore my phone back to the rom manager stock backup through recovery menu restore option before flashing it to another rom. That seemed to work fine.
Is there a reason for this? or is the rom manager backup different from a nandroid "backup all"?
dsu said:
Is there a reason for this? or is the rom manager backup different from a nandroid "backup all"?
Click to expand...
Click to collapse
No they are the same, may be better if you tell me what toy want to do, I don't know how to explain this in different terms. Restoring your rom manager backup does not qualify as flashing stock if that is what you are doing
Please someone tell me how to backup using nandroid. I've tried many times using ROM Manager but still stuck on recovery 3(e). My captivate run on froyo JI6. Thanks.
max_82 said:
Please someone tell me how to backup using nandroid. I've tried many times using ROM Manager but still stuck on recovery 3(e). My captivate run on froyo JI6. Thanks.
Click to expand...
Click to collapse
Get into recovery using power menu. Then you can use backup/restore to backup the rom.
Hey guys,
I used odin to get boot it back up and then I used ClockworkMod to restore backed up data....
After phone said 'restore complete,' I let the phone reboot, but the phone will not reboot
at&t screen pops up and then black out then pops up again then into android recovery mode.
Any ideas?
Could you please provide a little more information about how you got to where you are? (e.g. what rom/kernel/modem/theme you were flashing, what ODIN you used, what version of CWM, etc.) Anything you provide will be helpful in troubleshooting.
Well I had cognitive 4.5.3 installed and I tried restoring using clockmod recovery
the restore wasn't successful and the phone would stay black screened after Galaxy S logo screen
So I turned on odin3 and put my phone on download mode then hit start on odin3
that successfully restored the phone to froyo 2.2 without any of my data
so I tried using clockmod recovery once again to restore the backup
and then... that's where I am
The phone won't boot. It will just go into recovery mode
Here's the message I got after trying to restore once again
--------------------------------
ClockworkMod Recovery v2.5.1.2
Checking MD5 sums...
Restoring system...
Restoring data...
Restoring datadata...
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.
Restoring cache...
sd-ext.img not found. Skipping restore of /sd-ext/.
Restore complete!
--------------------------------
When did you make that nandroid backup? If you made it while on stock, you'll have to go back to stock first, then run the restore command. If on cognition, you'll need to be on the version you were on when you made the backup and restore there.
Here's the link I found on how to return to stock rom
http://forum.xda-developers.com/showthread.php?t=731989
I've done the first part - before the master reset and then tried restoring the backup and that is how I got to where I am right now.
Do I need to factory reset as well?
If I do factory reset, won't that erase the backup file?
Thanks. I really appreciate your help
jc830 said:
Here's the link I found on how to return to stock rom
http://forum.xda-developers.com/showthread.php?t=731989
I've done the first part - before the master reset and then tried restoring the backup and that is how I got to where I am right now.
Do I need to factory reset as well?
If I do factory reset, won't that erase the backup file?
Thanks. I really appreciate your help
Click to expand...
Click to collapse
To answer your question, doing the master clear will erase EVERYTHING stored in the phone's internal memory. Don't do that step now, as you should be able to get out of where you are without doing that.
I think where your problem occurred is that at some point you made a nandroid backup in CWM, and by trying to restore that on stock, it's freaking out. If you can remember what ROM setup you had on your phone when you made the backup, you could try to get back to that setup to use the restore option in CWM.
Before doing any of the things you're doing now, had you made a backup in Titanium Backup?
I do have backup made with Titanium Backup.
apps data and everything that I could backup with Titanium Backup
Will restoring what I had backed up with Titanium Backup and then restoring the system using CWM work?
I am currently at 2.2 Froyo, which was the rom I was using when backing up using CWM
You've flashed 2.2 stock? If so just flash the rom you previously had with cwm then let it boot. After it boots reboot into cwm then perform a restore in cwm. If that doesnt work nand backup might not be good and you will just have to flash stock again and just rub tibu and leave it at that.
**Thing about NAND backups is that you have to use the same system when you restore (i.e. you nand backup usng cognition then you flash another rom when you nand restore its not going to boot).
Thanks guys for the suggestions!
My phone has been saved!