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 currently have Cognition beta 6 installed and want to reflash or update to beta 9. How can I backup my apps, settings and media? It’s my understanding that TiB is for only apps and will not do non-app-phone-settings (possibly not app settings ether?)? Correct me if I’m wrong on that. Also, should I use Nandroid?
________________________
From the CogWiki:
Can I do an Nandroid Backup when the install is done?
If you are running CogYo beta 6 or later OR Cognition for Eclair, yes, as we can once again get back into Clockwork Recovery.
If you are running beta 5.5 or earlier, no, you can't currently do a clockwork nandroid backup as its not compatible with 2.2's new recovery (3e) without performing the "kernel swap" trick. You can update to a newer version of CogYo or revert to Eclair to re-institute this functionality.
__________________________
I am at CogB6 so this applies but I’m not entirely sure what it means.
In summary what can I do to get a comprehensive backup and subsequent restore after a reflash?
Thanks,
JOe K.
Several different things to address first your main question. Yes you need titanium backup. Its a great app and a lifesaver. As for moving phone settings thats when things get tricky. I tried restoring system apps and had horrible luck. It is going to mess things up bc the settings won't be the same and will cause funky bugs. Save your self some time and don't try to move your system settings from version to version.
2nd question clockwork basically makes a complete copy of your phone with all settings apps texts contacts etc. but it is only useful if you screw something up and need to restore your phone to a previous version
Sent from my SAMSUNG-SGH-I897 using XDA App
Hey guys, new here but I have been lurking for a while.
On Androidforums I have a longer thread detailing what I did, if you want details pm me, I can't post a link yet as I am a noob on this forum.
To make a long story short:
1. I had stock eclair, then rooted with "ryans oclf" and used the lagfix.
2. I decided to try a version of cognition (unhelpfuls kernal). So I backed up my current "rom" using rom managers (which was the stock kernal).
3. Realized that I didn't back anything up so I tried to revert to my backup.
4. relized that I didn't undo the lag fix, and because of this my stock eclair wouldn't restore via rom manger's update.zip file
5. was forced to get cognition running again
6. extraded the files from the .img nandroid bacups from my stock eclair (which is a PITA since the .img files aren't regular mountable .img files - took about an hour of searching)
7. Found the sql databases to restore my text messages and contacts from my stock eclair to this new cognition.
NOW, after a long intro, my question:
The .img files I extracted contained a file named linux.ex2. I assume that this file is where ryans oclf must have been storing the stuff that is causing the restore to fail (it actually completes, but never boots)
Is there any way I can manually repair this nandroid backup? I would like to so that I have a nandroid backup of my stock eclair rom.
BTW, I am pretty good at this kind of thing, but I am not a computer programmer.
I don't have a lot of background info directly related to andorid phones but I am learning quick. I am a Senior in electrical and computer engineering so I do have a light background in programming. luckily I knew enough about sql and command prompts and such to get as far as I did with recovering my contacts/text messages.
If what I want to do is possible I would love to give it a shot. Any help/tips/ideas from you guys would be awesome!
Thanks
-Chad
To me it sounds like your screwed. You did a double bummer.. (backup with LF on, restore a backup with LF ON on your already LF ON rom).
Will see if any other more experienced with backup can help you out, but my answer to you is to go stock and redo sorry.
yeah, well I am willing to try a few different things. I forgot to mention that right before I installed cognition the first time, I did remove the lag fix, I just undid the lagfix before I made the backup.
I have been using cognition for about a week now. I don't really mind it as it seems to work just fine, as It is in fact faster.
Last night after posting my post here I removed the voodoo lag fix and then I made a backup of my current installation of cognition.... So if I have any issues trying to do this I at least have a working/functioning cognition rom.
BTW: I have an unrelated question that is slightly related. If I have to use the odin one click restore at some point, does it clear my internal sd card as well? I see that it says it will clear user data, but doesn't specifically make a clear separation of the internal SD card on the captivate and the 2 gb they setup for the android partition.
A far faster method would be to Odin back to stock, root, then take a nandroid backup right away, then flash back to what ever rom you want. Time consuming, yes, but faster and easier than trying to mod a backup.
So im wondering, what is the standard practise, or based on your own experiences. What is the best way to flash over an existing rom using CWM? What do you do to prepare the fone for new rom, wipe user data, dalvik cache, before or after flashing. Just trying to get a good idea of how to do it.
Sent from my SAMSUNG-SGH-I897 using XDA App
going from rom to rom:
put rom.zip on /sdcard/
reboot to recovery
install zip from sdcard
point to rom.zip
flash
reboot
any rom that has been properly done will wipe user data and dalvik cache for you. no need to do it manually
i always flash back to eclair and master clear with odin one click to make sure all files from previous roms are gone then CWM flash new ROM
Pirateghost said:
going from rom to rom:
put rom.zip on /sdcard/
reboot to recovery
install zip from sdcard
point to rom.zip
flash
reboot
any rom that has been properly done will wipe user data and dalvik cache for you. no need to do it manually
Click to expand...
Click to collapse
+1
Except I do clear the caches manually, but that's just because I have OCD.
CremeFraiche said:
i always flash back to eclair and master clear with odin one click to make sure all files from previous roms are gone then CWM flash new ROM
Click to expand...
Click to collapse
lets look at the master clear function shall we?
when you flash to stock...your entire / is stock (RFS, eclair 2.1, /data /system, etc)
essentially, you have just reformatted your root, think of it like formatting your C drive and your sdcard is like a secondary internal drive that contains storage
master clear at this point will only delete items off your /sdcard
roms dont care about your /sdcard, master clear is worthless when you are stock
there was a time where it was necessary to flash to stock to reset the filesystem and then flash the rom. it has not been needed in months, but it continues to get preached as gospel.
even flashing to stock isnt necessary unless you are trying to come from CM7 or MIUI....or if something goes horribly wrong
Thx for info guys, I have flashed a few times and it seemed like now and then my fone must became bogged down and needed to be fully wiped, sound didnt work or lagfix folders bunch of text docs, just seemed cluttered. So if wanted to really clear out junk what would be a good way without having to flash back to stock?
Sent from my SAMSUNG-SGH-I897 using XDA App
Just flash. If you have a problem then back to stock Ans a MC. I have flashed hundreds of time back to stock once.
Sent from my SGH-I897 using XDA Premium App
Pirateghost said:
lets look at the master clear function shall we?
when you flash to stock...your entire / is stock (RFS, eclair 2.1, /data /system, etc)
essentially, you have just reformatted your root, think of it like formatting your C drive and your sdcard is like a secondary internal drive that contains storage
master clear at this point will only delete items off your /sdcard
roms dont care about your /sdcard, master clear is worthless when you are stock
there was a time where it was necessary to flash to stock to reset the filesystem and then flash the rom. it has not been needed in months, but it continues to get preached as gospel.
even flashing to stock isnt necessary unless you are trying to come from CM7 or MIUI....or if something goes horribly wrong
Click to expand...
Click to collapse
I would definitely agree. I have also seen people say to disable lagfix before flashing. I have not done that either and never had any problem.
Would just like to amend the advice already given with the following:
Pre-flashing:
1. Titanium Backup of apps and data
2. Nandroid backup in case something goes boom.
Post-flashing (assuming success):
TB restore of user apps/data only. NEVER RESTORE SYSTEM FILES.
They may not apply to some people, but I feel those are necessary steps for anyone that actually uses their phone daily.
modest_mandroid said:
Would just like to amend the advice already given with the following:
Pre-flashing:
1. Titanium Backup of apps and data
2. Nandroid backup in case something goes boom.
Post-flashing (assuming success):
TB restore of user apps/data only. NEVER RESTORE SYSTEM FILES.
They may not apply to some people, but I feel those are necessary steps for anyone that actually uses their phone daily.
Click to expand...
Click to collapse
why not restore system files? Does this apply if coming from flashing back to stock first, or just flashing from one rom to another?
Glad to hear the advice about not flashing back to stock, that's been one of the major reasons I haven't flashed quite as many rom's as I want, too time consuming.........not to say that i'm not flashing a couple rom's a week, but there's just so many options to try
neophile said:
why not restore system files? Does this apply if coming from flashing back to stock first, or just flashing from one rom to another?
Click to expand...
Click to collapse
Making "search" a standard practice would be very helpful.
Restoring system is known to mess up ROMs in all cases. Though may not be mandatory, but make it a standard practice to flash stock. Takes hardly 10 mins, and helps save big headaches later.
neophile said:
why not restore system files? Does this apply if coming from flashing back to stock first, or just flashing from one rom to another?
Click to expand...
Click to collapse
Incompatibilities across rom versions, mostly. As the guy above me said, restoring system files tends to mess up a rom because you are overwriting part of it with files from a different rom.
There is one caveat, however. If you're flashing back to a rom you originally performed the backup on, you can safely restore system files. For example, if you were running Cog 4.3 and did a full TB backup, then decided to flash Serendipity 6.3, you would want to restore only your user apps and user data. However, if you decided to flash back to Cog 4.3 at some point, you could do a full TB restore without worrying about incompatibilities.
I agree with everyone else. Flashing over another rom seldom causes issues. I make s nandroid backup of my favorite rom with everything setup the way i like it. then flash away trying different roms. When i am done, i just restore my backup and all is good!
I have done a search, couldn't find the specific answer I needed, hence my asking. Could be I wasn't phrasing the search correctly......but here I am.....
To clarify, what do you dpo to get your system settings back after flashing a new rom? I flashed to serendipty 6.4 last night, as per the advice, I didn't restore system files, just apps and data, but that didn't work so well for me. I lost my data connection, could only use my wifi, and had no contacts, or any sms msgs. I don't know what else was missing, but I then went and restored system files, everything came back as needed, and there seems to be no issue......
How do I get my info setting back, or do I just need to manually re-set everything after flashing? Apart from wireless info, msgs and contacts, what else do you lose by not restoring?
Appreciate your help
havent flashed a new rom in a while and forgot if anything extra was needed when flashing a rom over a rom
thx!
I have to take my daughter's Cappy in for a warranty exchange because of battery draining too fast. She was running Fasty 2.4 and had to go back to stock. I restored with the nandroid backup we created before. I may have screwed things up a bit because of restoring that way.
Although we got back to stock, none of her apps returned in the drawer, including Android Market. The only apps in the drawer are bloatware and superuser. CWM recovery is available. There is no My Files either. Did I miss a step in doing the nandroid restore? Hoping we can get her apps back. Really don't want to take the phone back with so much missing.
Thanks for any advice.
Sent from my FASTY 2.4 Captivate using Tapatalk.
Reflash stock. Don't restore the nandroid.
mrhaley30705 said:
Reflash stock. Don't restore the nandroid.
Click to expand...
Click to collapse
+1. To elaborate a little bit, just use odin one click to flash back to stock eclair. Dont restore anything on it just take it back after you flash and make sure its all together. But if you want all this stuff on your new captivate that you will root and flash I would make backup to an external SD card using titanium backup.