Sorry if this has been asked before but I have searched and didn't find any answers.
I have never been able to restore a nandroid backup on the Galaxy S. I go through the restore procedure in recovery and everything seems to restore correctly, no errors reported, says restore successful, but when the phone boots up from recovery it hangs on the boot screen.
I've tried with lots of different roms/kernels. I've wiped thoroughly before restoring. I'm even trying to restore from the same version, i.e. JVH or JVP, always the same result. I'm not trying to restore between cm7/samsung roms or froyo/gingerbread or even different versions. An example is, I was on Darky 10.1re. I did a nandroid. I tried a few other roms (F1, GingerReal, Tweaky), tried to nand back to Darky's, appears to restore without problems until the reboot where it hangs on boot screen. Also tried to restore to nadroids of the above roms with the same results.
Can anyone tell me where I'm going wrong, I'm sure I'm missing something really obvious as nobody else seems to be having trouble with backups.
Thanks.
I could imagine it would be hard to point out what the exact problem is, unless someone has experienced this issue before. Which I haven't, sorry. Not on my SGS, nor on my SGS2. But it sounds like a compatibility problem to me. You say you've never been able to restore, have you had the same problem with Darky ROMs prior to 10.x, perhaps 9.5? Have you used Darky's Dark Core kernel along with it?
The same thing is happening to me. Used to nandroid restore on froyo and never had a problem. The last 2 times that I tried to restore (with Ginger 2.3.3 and 2.3.4) I had problems, both times with Criskelo´s rom and Darkcore Kernel. The restore begins normally but suddenly stops and there is no way to revert the semi-brick other than odin. BTW, I never use lagfix.
Used nandroid backup and restore successfully on gingerbread on both speedmod and galaxian kernels
Sent using geek power
I have same problem and i ended using nandorid backup which is very usefull.
I think this started at beginning of Gingerbread kernels using.
bitmaster2000 said:
I could imagine it would be hard to point out what the exact problem is, unless someone has experienced this issue before. Which I haven't, sorry. Not on my SGS, nor on my SGS2. But it sounds like a compatibility problem to me. You say you've never been able to restore, have you had the same problem with Darky ROMs prior to 10.x, perhaps 9.5? Have you used Darky's Dark Core kernel along with it?
Click to expand...
Click to collapse
Thanks for your suggestions. The first rom I installed after buying my Galaxy S was the current Darky one at the time, v10 rc something. Didn't try the older ones. At first I always used the Dark Core kernel, even with other roms. Still couldn't restore.
I've also tried a mixture of roms/kernels since then with no luck with the nandroid.
Could it be something to do with the recovery? I noticed different roms/kernels install a different recovery. Maybe it's only possible to restore using the same recovery as was used to take the backup? But if this was the case, surely other people would be having the same problem?
Thanks.
eggshaped said:
Thanks for your suggestions. The first rom I installed after buying my Galaxy S was the current Darky one at the time, v10 rc something. Didn't try the older ones. At first I always used the Dark Core kernel, even with other roms. Still couldn't restore.
I've also tried a mixture of roms/kernels since then with no luck with the nandroid.
Could it be something to do with the recovery? I noticed different roms/kernels install a different recovery. Maybe it's only possible to restore using the same recovery as was used to take the backup? But if this was the case, surely other people would be having the same problem?
Thanks.
Click to expand...
Click to collapse
Darky kernel had a restore problem once but they solved it now.
"Changelog 2.5:
Fixed Nandroid Restore through CWM" from darky forum.
yken said:
Darky kernel had a restore problem once but they solved it now.
"Changelog 2.5:
Fixed Nandroid Restore through CWM" from darky forum.
Click to expand...
Click to collapse
Yes I remember reading about that. That's what I put it down to in the beginning, but now it's been fixed and it still doesn't work for me. Not even with other kernels.
Well, it's not the end of the world I suppose. Just makes me more reluctant to try different roms as I'm too lazy to go through the whole odin/flashing/restoring process every time lol.
Thanks for your suggestions guys
With Dark Core kernel 2.7.x and 2.8 i have the same problems when i'm on rfs, backup function is ok but restore doesn't work. With ext4 conversion enabled backup and restore work as they should.
I've found a solution, just in case anyone else is having the same problem this is how I got around it.
I downloaded and installing the latest cwm using Rom Manager, so any backups are taken on 3.0.0.5. When changing roms I had to download and install the same recovery with Rom Manager and restore using the same 3.0.0.5. For some reason it only works when using rom manager. If I try to restore manually in recovery it doesn't work. If I try to restore with any other recovery version it doesn't work. So for me my nandroid backups only restore between the exact same recovery versions.
Sounds fairly obvious now, after thinking about it lol, but this has been giving me a major headache for weeks now.
Related
Silly noob-like question, but I wanted to make sure before I continued messing with my phone.
Does ROM Manager back up EVERYTHING on the phone? For example, I backup my rom. Move the backup file onto my pc. Then I screw around with roms, lag fixes, etc. and totally screw it up. If I "restore" the backup made by ROM Manager, will all my apps, settings, desktop, data files, etc be exactly as they were before I started screwing around?
Or, would I need to use Odin to load the same ROM as that which was backed up and then run Rom Manager Restore?
Thanks!
Yes it does
Sent from my SAMSUNG-SGH-I897 using XDA App
Here's another question regarding this thread:
I have the lagfix mod which uses the internal sdcard. When I create a backup will it and restore exactly how it was including the lagfix partition? If yes, is it the same procedures or do I have to do it a different way with the extra partition?
Thanks in advance.
Deca4 said:
Here's another question regarding this thread:
I have the lagfix mod which uses the internal sdcard. When I create a backup will it and restore exactly how it was including the lagfix partition? If yes, is it the same procedures or do I have to do it a different way with the extra partition?
Thanks in advance.
Click to expand...
Click to collapse
Actually I am trying to figure out the same thing. I made a backup before I started messing around with lag fixes, different roms and so forth. Then the other day I tried to restore a rom it didn't work. Eventually I soft bricked the phone and had to make the USB Jig to get it working again. Needless to say I am very intrigued with what exactly Rom Manager does backup and its limitations but I can't seem to find it anywhere. I am thinking the reason my backup was screwed up was because of a lag fix, only problem is I can't remember what lag fix I had on it when I did the initial recovery.
Something from my experience to add here:
Scenario 1:
-----------
I backed up the original 2.1 JH7 on my phone.
Installed 2.2 custom ROM, and played around with it.
Backed up 2.2 ROM.
Messed up with my 2.2 custom ROM.
Went to ROM manager recovery, and recovered the backed up 2.1 JH7, and ended up messing up. My phone didn't even boot up.
Then I went back to recovery, and tried restoring the backed up version of 2.2.
Phone booted up into 2.2, but, started giving a lot of FCs.
Scenario 2:
-----------
Installed 2.2 custom ROM 1.
Backed it up.
Messed it.
Restored it - worked fine.
Installed 2.2 custom ROM 2.
Backed it up.
Restored the 2.2 custom ROM 1.
Everything working fine.
Looks like as long as the core OS is of the same version, it seems to work.
Maybe there is something in the boot sequence that's probably not being restored (???)
---------------
Edit: I do not have CWM app installed. I use the CWM update.zip recovery manager since its the least intrusive way.
diablo009 said:
Something from my experience to add here:
Scenario 1:
-----------
I backed up the original 2.1 JH7 on my phone.
Installed 2.2 custom ROM, and played around with it.
Backed up 2.2 ROM.
Messed up with my 2.2 custom ROM.
Went to ROM manager recovery, and recovered the backed up 2.1 JH7, and ended up messing up. My phone didn't even boot up.
Then I went back to recovery, and tried restoring the backed up version of 2.2.
Phone booted up into 2.2, but, started giving a lot of FCs.
Scenario 2:
-----------
Installed 2.2 custom ROM 1.
Backed it up.
Messed it.
Restored it - worked fine.
Installed 2.2 custom ROM 2.
Backed it up.
Restored the 2.2 custom ROM 1.
Everything working fine.
Looks like as long as the core OS is of the same version, it seems to work.
Maybe there is something in the boot sequence that's probably not being restored (???)
---------------
Edit: I do not have CWM app installed. I use the CWM update.zip recovery manager since its the least intrusive way.
Click to expand...
Click to collapse
Interesting, it would makes sense in what you are saying. My error that I go was when I went from my original JH7 backup, installed a rom based on JH6 and then tried to install my original backup. I might have to try JH6 roms and see if I can restore to them easily or not. I will have to wait for Micro USB cables to come in as I don't have a spare since I used my only cable to make the JIG.
The kernel and modem aren't backed up, so if your backups use different ones and you try to restore them you'll have issues.
I herd a rumor that rom manager doesn't work with froyo on the captivate. But I could be totally wrong.
Sent from my SAMSUNG-SGH-I897 using XDA App
peachpuff said:
The kernel and modem aren't backed up, so if your backups use different ones and you try to restore them you'll have issues.
Click to expand...
Click to collapse
This is what I have read about it as well
Voodoo
There is also a different version of CWM Recovery (what Rom Manager uses to back things up) for the voodoo lag fix.
tnerb123 said:
I herd a rumor that rom manager doesn't work with froyo on the captivate. But I could be totally wrong.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It works. I backed up and restored a few variants of Froyo ROMs.
peachpuff said:
The kernel and modem aren't backed up, so if your backups use different ones and you try to restore them you'll have issues.
Click to expand...
Click to collapse
How do I backup these? Is there any way?
If Ron Manager does backup the kernel and modem why would so many people have problems restoring back to different Roms? This is why I am so puzzled with this software.
Sent from my SAMSUNG-SGH-I897 using XDA App
Rom Manager can backup EFS folder ??
i lost my imei and the only backup that i have its from Ron Manager
Absolutely it does there!
Maybe I'm old fashioned, but best bet is backup from recovery. Saves everything down to browser login data. Can't go wrong with a full backup! I make one every time I flash just about anything.
Sent from my SGH-I897 using xda app-developers app
Rom Manager vs CWM Recovery
yes Rom Manager can do backup of phone..but why not just do
a Nandroid Backup from CWM Recovery..
never had problem with Nandroid Backup from CWM Recovery :victory:
dobi3 said:
yes Rom Manager can do backup of phone..but why not just do
a Nandroid Backup from CWM Recovery..
never had problem with Nandroid Backup from CWM Recovery :victory:
Click to expand...
Click to collapse
Agreed!
Sent from my SGH-I897 using xda app-developers app
I have flashed a couple roms to my phone I take all the right steps flashing back to stock rom first and all. But any rom I flash after a day my phone starts vibrating and resets it self. Can some one help.
You need to post more info....what rom, what are you restoring after flashing, what are you doing when the problem occurs..
I was flashing cognition 2.3b6, even happens with regular froyo rom. When it resets I'm not doing anything. Just vibrates and resets.
Obviously something is causing your soft reboots.....this can be caused by many things but should not occur unless something is being modified such framework or you are restoring something from 2.1 that is not compatible with 2.2
After you flash to 2.2, what steps do you take, ie do you use titanium backup to restore apps and/or data? Are you applying any mods such as custom battery?
No I don't use nothing besides the rom. I even formatted my card.
Confused then....i have flashed many different roms including cog and have not had problems unless I do something that causes it
I would try a different rom....axura is great, the i9000 ports are nice as well.
Sorry I cannot help more
Before you flash, try wiping the dalvik cache. See if that helps.
Swyping...please read slowly!
don't know how to do that is that the same as the user catch.
kingtrini82 said:
don't know how to do that is that the same as the user catch.
Click to expand...
Click to collapse
In CWM, under advanced. Take a gander.
So I have tried many times to restore my phone from a backup made by recovery manager, but it never seems to work. It will always make it to the desktop, but either restart constantly or everything will constantly crash making it unusable. Is there something I'm doing wrong?
Sent from my SAMSUNG-SGH-I896 using XDA App
Is your back up the same base as what toy are on. Meaning 2.1 to 2.1. Are you trying to restore a stock backup over 2.2?
mcord11758 said:
Is your back up the same base as what toy are on. Meaning 2.1 to 2.1. Are you trying to restore a stock backup over 2.2?
Click to expand...
Click to collapse
No. The ROM I was running when doing the backup was Serendipity 3.0. I flashed back to Serendipity 3.0, then ran my restore. Everything constantly crashes.
EDIT: I've found uninstalling and reinstalling the applications works, but then there's no point in making a nandroid backup. I might as well just flash back to the ROM I was on and use TiBu in that case.
Anyone else have any ideas?
I'd really like to experiment more with ROMs and custom projects, but I don't want to unless I can basically go back to what I had with one click.
Get titanium backup pro. lts $5, but well worth it. Everything restores with one click.
Sent from my SAMSUNG-SGH-I897 using XDA App
sixstringsg said:
Get titanium backup pro. lts $5, but well worth it. Everything restores with one click.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yeah, I guess I'll just backup absolutely everything with TiBU Pro and keep the installation files around for each ROM, since CWM backups do not seem to work properly.
Auridran said:
Yeah, I guess I'll just backup absolutely everything with TiBU Pro and keep the installation files around for each ROM, since CWM backups do not seem to work properly.
Click to expand...
Click to collapse
CWM backups work fine as long as you have matching firmware versions (2.1-2.1, 2.2-2.2, or 2.2.1-2.2.1)
also you need to be aware of lagfixes in the rom that you may currently be running, they are not always compatible between roms
nandroid does not backup your kernel or modem which is why you need to be moving within the same firmware versions
you cant make a stock nandroid backup, flash a 2.2 rom, then restore from that backup immediately. you will need to do a couple of things first.
keep a stock 2.1 cwm flashable kernel and modem on your sdcard
revert any lagfixes your phone may have prior to trying to restore your nandroid of stock
once lagfixes are removed, flash your kernel and modem (same firmware version as your nandroid backup)(its possible to have this set up within ONE zip file)
once you are rebooted back into CWM, restore your nandroid...reboot and profit
Pirateghost said:
CWM backups work fine as long as you have matching firmware versions (2.1-2.1, 2.2-2.2, or 2.2.1-2.2.1)
also you need to be aware of lagfixes in the rom that you may currently be running, they are not always compatible between roms
nandroid does not backup your kernel or modem which is why you need to be moving within the same firmware versions
you cant make a stock nandroid backup, flash a 2.2 rom, then restore from that backup immediately. you will need to do a couple of things first.
keep a stock 2.1 cwm flashable kernel and modem on your sdcard
revert any lagfixes your phone may have prior to trying to restore your nandroid of stock
once lagfixes are removed, flash your kernel and modem (same firmware version as your nandroid backup)(its possible to have this set up within ONE zip file)
once you are rebooted back into CWM, restore your nandroid...reboot and profit
Click to expand...
Click to collapse
Well like I said, I made a backup on my Serendipity 3.0 ROM I had going, flashed to something else, then even flashed back to Serendipity 3.0 before restoring and it still didn't work properly. All the apps I had installed just force-closed until I reinstalled them, or force-closed somewhere during use.
Trying to create a nandroid backup in cement v4... (running uckj3, with boog's kj3 kernel) and every time i boot into recovery and perform a backup it gets stuck at "backup sd-ext" kinda confused as to why this is happening, also can't get the kj3 extended power menu to work, flashed the zip maybe 5 times, cleared the cache/dalvik cache and nothing, any and all suggestions are greatly appreciated. Thanks guys.
Sent from my SAMSUNG-SGH-I897, named Ginger, using XDA App.
The nandroid backup is not yet working in the Gingerbread Roms.
The extended power menu is for Deodexed Roms only.
Hope this info proves helpful.
update
Okay, so I was thinking about why it wasn't working and went to my clockworkmod folder on the SD and saw that the files were pretty large in size, all totally over 4 FBI, so i deleted some miscellaneous files to free up some additional space and tried to run cement backup again... still took a while and did think it got stuck again, but it actually finished..could i safely assume that it worked or should i not trust the files? Also, the more i think about it, do i really need a Nan backup? Meaning, if anything goes wrong with my phone i can always reflash stock and use titanium backup to restore my apps...any thoughts?
Like I said before, the Nandroid Backup does not work in the Gingerbread world. It may look like it is backing up but the restore part won't happen. If u try u may soft brick.
And yes, the fail safe is that you could always return to a Gingerbread stock of your choice and use Titanium Backup to restore your stuff.
nandroid works on gingerbread, just not I897 kernels. I9000 works fine.
although i don't use them personally.
^ Thanks for the clarification. I didn't realize that about the i9000 because I am always on i897.
It's amazing what is being accomplished on captivate kernels, reverse engineering and building "blind" but nothing beats having source code to work with, which is why the I9000 nandroid works.
So how can I tell if I'm running an I897 or I9000? Currently using UCKJ3 with boogs kernel and just flashed the samurai kernel
Sent from my SAMSUNG-SGH-I897 using XDA App
that is I897.
I897 firmwares usually start with a K
I9000 usualy a J
it will also usually say in the op of the thread...
Hey all,
I installed CM10 Helly Bean (DerTeufel) port for Captivate V10 with full wipe.
It seemed to be working fine... fooled around a bit, tried out Google Now, etc.
Was restoring apps (not data) w/ Titanium Backup.. forget if it had finished or not...
Didn't try to run any of these programs or anything, just tried to unlock and the touchscreen was not responsive... Tried wiping cache+dalvik + fixing permissions... tried reinstalling ROM and GAPPS...
All are in a non-responsive bootloop.
I'm starting over now with another factory wipe... as of now it is stuck on "Welcome" Screen and touchscreen is not responding... AND.. it just restarted
Any ideas as to the problem... Was it Titanium Backup related? Should I resist running that again (assuming this ever works)?
I would post this on Development thread but I still don't have my 10 posts, heh, mostly a long-time lurker...
Thanks!
Worse than I thought!
So It's worse than I thought... I gave up and re-flashed slim (ICS)... and the same problem still exists... boots up, looks normal, can't touch anything.... eventually it reboots....
Suggestions?
Would ODIN flash do anything different? I9000 bootloaders?
ScruffMcG said:
Hey all,
I installed CM10 Helly Bean (DerTeufel) port for Captivate V10 with full wipe.
It seemed to be working fine... fooled around a bit, tried out Google Now, etc.
Was restoring apps (not data) w/ Titanium Backup.. forget if it had finished or not...
Didn't try to run any of these programs or anything, just tried to unlock and the touchscreen was not responsive... Tried wiping cache+dalvik + fixing permissions... tried reinstalling ROM and GAPPS...
All are in a non-responsive bootloop.
I'm starting over now with another factory wipe... as of now it is stuck on "Welcome" Screen and touchscreen is not responding... AND.. it just restarted
Any ideas as to the problem... Was it Titanium Backup related? Should I resist running that again (assuming this ever works)?
I would post this on Development thread but I still don't have my 10 posts, heh, mostly a long-time lurker...
Thanks!
Click to expand...
Click to collapse
sorry I'm just going to post twice so I can post to development...
yeah... 10char
What I can suggest is, go back to GB. Download a one click Odin w/ bootloaders, you can search that in the dev forum. After that flash it with a corn kernel so you can have a working CWM. And then Go to recovery, have a full wipe (data,cache,dalvik) TWICE and flash this--
Slimmed Down V10 by cbalt
Wipe Data/Factory Reset/Wipe Dalvik
Flash http://www.mediafire.com/?9p212pempybwnj3
Then Flash http://www.mediafire.com/download.php?bdjabcmobz6aw6k
Then Fix Permissions
Then Reboot
Click to expand...
Click to collapse
I can recommend you that one because it's the one the I'm currently using right now and I can say that it's working like a charm.
The method above is the one I'm using everytime I flash a ROM. I always do a full wipe so I won't be encountering any issues or whatsoever.
About TiBu, I am not sure if that's where the issue coming from because I've been using TiBu for a long time and haven't encountered that. Just always remember, if you are using backup using TiBu, just backup the User Apps+Data, DO NOT INCLUDE THE SYSTEM APP. Goodluck!
So you think w/bootloaders will help?
I have flashed every odin w/o bootloaders that I have access too and all get me stuck at ATT bootscreen....
Little hesitant to reflash my bootloaders since I was/am already on GB bootloaders, but if it might help I may have to do it...
I actually was on that JB version (but with the normal gapps b/c I wanted google now...)... now I'm on no version of anything hahah
takeoutttt said:
What I can suggest is, go back to GB. Download a one click Odin w/ bootloaders, you can search that in the dev forum. After that flash it with a corn kernel so you can have a working CWM. And then Go to recovery, have a full wipe (data,cache,dalvik) TWICE and flash this--
I can recommend you that one because it's the one the I'm currently using right now and I can say that it's working like a charm.
The method above is the one I'm using everytime I flash a ROM. I always do a full wipe so I won't be encountering any issues or whatsoever.
About TiBu, I am not sure if that's where the issue coming from because I've been using TiBu for a long time and haven't encountered that. Just always remember, if you are using backup using TiBu, just backup the User Apps+Data, DO NOT INCLUDE THE SYSTEM APP. Goodluck!
Click to expand...
Click to collapse
I met a problem. I do not know wether or not it is common. The phone will reboot by itself sometimes.
Do you have the same problem?
same here
seems as though many of the problems experienced by one are shared by the other
this is logical as they share many common points including the same partition and both jellybean derivations
I was having issues... accelerometer and audio issues.
All came out right as rain after flashing back to stock and reflashing
ScruffMcG said:
yeah... 10char
Click to expand...
Click to collapse