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
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.
Will this option on the main screen format the internal SD? I don't want to lose all my data.
I can't seem to get nandroid to ever properly restore. I have a backup of CM6/1, and restoring it from a clean JH2 install soft bricked my phone. Odin'd back to JH2. I just didn't know what to do, so I ask my cousin, who has an N1. He says before retoring backups you have to do Wipe Data/Factory Reset option in Clockwork. I know it doesn't wipe your SD, but since Captivate's is internal will it wipe all my user data, like photos and music?
Also any advice on nandroid?
EDIT: Also it seems nandroid doesn't restore kernel. Because when i go from JH2 to CM6.1, the kernels splash screen at boot remains AT&T where it gets stuck and never boots, when it should be the i900 splash screen.
Haloruler64 said:
Will this option on the main screen format the internal SD? I don't want to lose all my data.
I can't seem to get nandroid to ever properly restore. I have a backup of CM6/1, and restoring it from a clean JH2 install soft bricked my phone. Odin'd back to JH2. I just didn't know what to do, so I ask my cousin, who has an N1. He says before retoring backups you have to do Wipe Data/Factory Reset option in Clockwork. I know it doesn't wipe your SD, but since Captivate's is internal will it wipe all my user data, like photos and music?
Also any advice on nandroid?
EDIT: Also it seems nandroid doesn't restore kernel. Because when i go from JH2 to CM6.1, the kernels splash screen at boot remains AT&T where it gets stuck and never boots, when it should be the i900 splash screen.
Click to expand...
Click to collapse
The only good way for Nandroid to help you is if you have your Nandroid backup stored somewhere other than IntSD.
If you are on a different kernel or modem, my suggestion is to flash stock, master clear, flash the cognition version that the nandroid was based on, then restore your nandroid backup.
daverup said:
The only good way for Nandroid to help you is if you have your Nandroid backup stored somewhere other than IntSD.
If you are on a different kernel or modem, my suggestion is to flash stock, master clear, flash the cognition version that the nandroid was based on, then restore your nandroid backup.
Click to expand...
Click to collapse
So I'd have to flash stock, flash Cog, flash CM, then restore backup? Wow... N1 is dead simple, just wipe data and restore.
Any idea what Wipe Data/Factory Restore option in CMW actually means in terms of affecting Internal SD?
Also how do you restore from a backup on extSD?
Haloruler64 said:
So I'd have to flash stock, flash Cog, flash CM, then restore backup? Wow... N1 is dead simple, just wipe data and restore.
Any idea what Wipe Data/Factory Restore option in CMW actually means in terms of affecting Internal SD?
Also how do you restore from a backup on extSD?
Click to expand...
Click to collapse
I think the wipe data in cw refers to phone memory. I don't think I remember that ever affecting IntSD.
The backup in the clockworkmod dir can be moved back and forth and still work. I just copy the whole clockworkmod dir off of the IntSD to the Ext SD, moving it back as needed.
Flashing CWM is really overcomplicating things. If you have the CW 1.7mb update.zip file in the root of your IntSD, and can boot recovery. Then you can re-install packages and CWM will run.
daverup said:
I think the wipe data in cw refers to phone memory. I don't think I remember that ever affecting IntSD.
The backup in the clockworkmod dir can be moved back and forth and still work. I just copy the whole clockworkmod dir off of the IntSD to the Ext SD, moving it back as needed.
Flashing CWM is really overcomplicating things. If you have the CW 1.7mb update.zip file in the root of your IntSD, and can boot recovery. Then you can re-install packages and CWM will run.
Click to expand...
Click to collapse
Thanks, ill try it.
Oh, copying? Thanks for that info man, much appreciated.
And no, lol, not CWM, CM, as in CyanogenMod. You have to flash it over Cognition to have it run properly.
I can confirm Wipe Data/Factory Reset doesn't affect your user data like IntSD and ExtSD.
But I can not solve the nandroid issue. I flashed to stock, flashed Cog, flashed CM6.1, and restored my CM backup, won't boot.
Well does it boot the fresh CM6.1? and did you let Voodoo convert data when you booted up Cog?
ps didnt flash this. Just trying to get more information.
Maybe try reflashing CM6.1.
JimmehDean said:
Well does it boot the fresh CM6.1? and did you let Voodoo convert data when you booted up Cog?
ps didnt flash this. Just trying to get more information.
Click to expand...
Click to collapse
At what part of my process are you referring to? Fresh installs from Cog (with Voodoo enabled after a boot) to CM work perfectly. Flashing Cog, enabling voodoo, then flashing CM, then restoring from backup soft bricks it (never boots), any restore from backup soft bricks it
Rhiannon224 said:
Maybe try reflashing CM6.1.
Click to expand...
Click to collapse
I flashed CM6.1 many times and tried to restore from backup, from CM, from stock, nothing works. Only a fresh install (what I have now) works. My problem isn't getting my phone working, it's figuring out why nandroid won't work
Haloruler64 said:
I flashed CM6.1 many times and tried to restore from backup, from CM, from stock, nothing works. Only a fresh install (what I have now) works. My problem isn't getting my phone working, it's figuring out why nandroid won't work
Click to expand...
Click to collapse
I had this happen a while back, I believe the lagfix messed up my Nandroid Backups, none of them worked after installing the lagfix, not Voodoo, the ULF with Setiron's kernel.
Rhiannon224 said:
I had this happen a while back, I believe the lagfix messed up my Nandroid Backups, none of them worked after installing the lagfix, not Voodoo, the ULF with Setiron's kernel.
Click to expand...
Click to collapse
so with Voodoo on, nandroid backups will not work even when they were created with Voodoo off? Will nandroids with Voodoo on work if they were created with Voodoo on? Does anyone know this lol
Haloruler64 said:
so with Voodoo on, nandroid backups will not work even when they were created with Voodoo off? Will nandroids with Voodoo on work if they were created with Voodoo on? Does anyone know this lol
Click to expand...
Click to collapse
I don't know, I just know that when I originally installed Setiron's kernel and ULF my Nandroid Backups were worthless, they must have gotten corrupted, thankfully I had them stored on my pc so they weren't lost. Depends on which Voodoo kernel, Unhelpful's dosen't work with CW if Voodoo isn't disabled, if you're using DG's you'd have to ask him, go to the IRC Cognition chat and ask them. Someone there will be able to help. I always disable voodoo before using backups with CW.
Rhiannon224 said:
I don't know, I just know that when I originally installed Setiron's kernel and ULF my Nandroid Backups were worthless, they must have gotten corrupted, thankfully I had them stored on my pc so they weren't lost. Depends on which Voodoo kernel, Unhelpful's dosen't work with CW if Voodoo isn't disabled, if you're using DG's you'd have to ask him, go to the IRC Cognition chat and ask them. Someone there will be able to help. I always disable voodoo before using backups with CW.
Click to expand...
Click to collapse
I just think nandroid on Captivates doesnt actually affect the kernel. i897 kernels ahve AT&T splash screen, while i9000 have i9000 ones. From JH2 (no voodoo), restoring CM6.1 (made when Voodoo was off) soft bricked my phone. On boot, it showed the AT&T screen and got stuck there. So I assume it never flashed back the kernel from CM6.1
Haloruler64 said:
I just think nandroid on Captivates doesnt actually affect the kernel. i897 kernels ahve AT&T splash screen, while i9000 have i9000 ones. From JH2 (no voodoo), restoring CM6.1 (made when Voodoo was off) soft bricked my phone. On boot, it showed the AT&T screen and got stuck there. So I assume it never flashed back the kernel from CM6.1
Click to expand...
Click to collapse
It dosen't touch the kernel. That is a pain, I forgot about that once, soft bricked and never forgot to flash the kernel before installing backup again. You can't restore a backup of CM6.1 over JH7, it is a 2.1 kernel for starters. CM6.1 is 2.2, huge pronlem. You need a 2.2 I9000 kernel.
Rhiannon224 said:
It dosen't touch the kernel. That is a pain, I forgot about that once, soft bricked and never forgot to flash the kernel before installing backup again. You can't restore a backup of CM6.1 over JH7, it is a 2.1 kernel for starters. CM6.1 is 2.2, huge pronlem. You need a 2.2 I9000 kernel.
Click to expand...
Click to collapse
The thing is, it backs up the kernel on the N1, and that was my basis. That explains why backups don't work even on Cognition, different kernel
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!
I tried restoring from a nandroid backup I made and after the restore, I could only get as far as the i9000 boot screen. I went into recovery to try and flash a ROM, but CMW recovery could not mount my partitions (partitions got messed up by nandroid?) The only quick way I could think of was to use odin and refalsh and repartition.
I restored my nandroid from within CWM recovery. Is there something I am missing in the restore process? Obviously something went wrong.
asicman said:
I tried restoring from a nandroid backup I made and after the restore, I could only get as far as the i9000 boot screen. I went into recovery to try and flash a ROM, but CMW recovery could not mount my partitions (partitions got messed up by nandroid?) The only quick way I could think of was to use odin and refalsh and repartition.
I restored my nandroid from within CWM recovery. Is there something I am missing in the restore process? Obviously something went wrong.
Click to expand...
Click to collapse
Hey man, sounds like you tried to restore one system over another,
Forexample, stock over cm7? and that messes up the partitions as you see!
Try to install the rom you are trying to restore before you start restoring!
Should work then!
Hope this helps
I did indeed try to restore a ROM which was very different from the installed ROM. I will keep your suggestion in mind the next time I do a restore.
Just to confirm : yes, you need to flash the base ROM you're trying to restore.
I played with ICS over the weekend and got back by flashing a stock - well stock+ - JVZ and restoring nandroid.
Did the same thing, stupid as I am,
the big problem is that none of the computers I've tried with is detecting my phone right now.
I get in to CWM but and to download mode but that ain't helping me since i can't use Odin to flash back to stock rom.
Any ideas?