[Q] Proper backup help - Droid Incredible Q&A, Help & Troubleshooting

I am running Virtuous and it is running smooth as butter, but I would like to try one of the CM7 nighly, and want to be able to go back if need be with out hours of work. I am running clockwork recovery and rom manager, and also have titaium back up installed. Phone is rooted with s-off. Can I just run a back up from rom manager do a complete wipe and install CM7. I also need to update hboot from .79 to .92 should this be done prior to the rom manager back up. Should CM7 not work out how do I restore back? Thanks

Yeah just nandroid (which means backing up the rom and all your settings) and you can go back at any time. In Rom manager just go to Backup current Rom and you will always have a copy of your setup EXACTLY as it is.
You can update HBOOT whenever you want, it really doesn't matter when you do it. Once you do it will stay that way.

Correct me if I'm wrong, but doesn't doing a nandroid backup essentially make a complete clone of your entire phone that you can restore later?

eman5oh said:
I am running Virtuous and it is running smooth as butter, but I would like to try one of the CM7 nighly, and want to be able to go back if need be with out hours of work. I am running clockwork recovery and rom manager, and also have titaium back up installed. Phone is rooted with s-off. Can I just run a back up from rom manager do a complete wipe and install CM7. I also need to update hboot from .79 to .92 should this be done prior to the rom manager back up. Should CM7 not work out how do I restore back? Thanks
Click to expand...
Click to collapse
Okay, here's what you to do back up:
1. Back up your apps with Titanium Backup - DO NOT BACK UP PHONE DATA. Backing up data for games (e.g. Angry Birds) is fine, but don't back up contacts or Gmail or anything that's going to be included in your new ROM. Reason is, when you restore everything (more on that later), you don't want to have conflicting data screwing things up.
2. Make a nandroid using ROM Manager. Just go to where it says backup current rom, and let it do it's magic. You can (and should) rename it to something you can remember. DO NOT USE SPACES. I like to name mine with the date, ROM name, and version number (e.g. 2-3-11_Virtuous_3.1.0)
3. After the backup finishes, install the new ROM - I always do this through ROM Manager.
4. When CM7 is finished installing, download Titanium Backup and restore your apps using the batch operation - it's a lot simpler than trying to find all your apps and download/install them yourself
5. To go back, simply click "Restore Backup" in ROM Manager and pick Virtuous and all your hard work will be restored
Enjoy!

I've had lots of trouble with ROM manager not restoring or backing up my current ROM properly.....it'll always say that the installation was aborted or say the file is corrupt
Sent from my ADR6300 using XDA App

AlpineM3 said:
I've had lots of trouble with ROM manager not restoring or backing up my current ROM properly.....it'll always say that the installation was aborted or say the file is corrupt
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
How much free space is left on your card? Format and try it with a clean card. I have never had a problem with it restoring anything of mine.

Zoon0n said:
Okay, here's what you to do back up:
1. Back up your apps with Titanium Backup - DO NOT BACK UP PHONE DATA. Backing up data for games (e.g. Angry Birds) is fine, but don't back up contacts or Gmail or anything that's going to be included in your new ROM. Reason is, when you restore everything (more on that later), you don't want to have conflicting data screwing things up.
2. Make a nandroid using ROM Manager. Just go to where it says backup current rom, and let it do it's magic. You can (and should) rename it to something you can remember. DO NOT USE SPACES. I like to name mine with the date, ROM name, and version number (e.g. 2-3-11_Virtuous_3.1.0)
3. After the backup finishes, install the new ROM - I always do this through ROM Manager.
4. When CM7 is finished installing, download Titanium Backup and restore your apps using the batch operation - it's a lot simpler than trying to find all your apps and download/install them yourself
5. To go back, simply click "Restore Backup" in ROM Manager and pick Virtuous and all your hard work will be restored
Enjoy!
Click to expand...
Click to collapse
Am I asking for trouble when backing up apps via titium, and switching roms? I thought that I read that somewhere? I have used app brain to do the restores, but it is a little slow. Also Thanks to everyone for the replies.

I've read that the newer versions of Clockwork are troublesome....anything after 2.5.05. I just went in and erased any previous ROM's that I don't use anymore to free up valuable space on the SD card. Hopefully it works, but the message error i've been getting......well not a message error, but my phone seems to freeze up while developing MD5sum. I read to leave it alone and it might take 10 min's actually, but just want to confirm this is true. Thanks.
g00s3y said:
How much free space is left on your card? Format and try it with a clean card. I have never had a problem with it restoring anything of mine.
Click to expand...
Click to collapse

AlpineM3 said:
I've read that the newer versions of Clockwork are troublesome....anything after 2.5.05. I just went in and erased any previous ROM's that I don't use anymore to free up valuable space on the SD card. Hopefully it works, but the message error i've been getting......well not a message error, but my phone seems to freeze up while developing MD5sum. I read to leave it alone and it might take 10 min's actually, but just want to confirm this is true. Thanks.
Click to expand...
Click to collapse
I use 2.5.1.2 and have never personally had any problem, sorry.

eman5oh said:
Am I asking for trouble when backing up apps via titium, and switching roms? I thought that I read that somewhere? I have used app brain to do the restores, but it is a little slow. Also Thanks to everyone for the replies.
Click to expand...
Click to collapse
I've gone from Stock to Virtuous to MIUI to CyanogenMod and I can say definitively that I have never had any problems with Titanium backing up/restoring apps. You are asking for trouble if you try to back up system data and restore it for ROM's that they were never intended for - just back up the apps you downloaded from the market/installed yourself and you'll be fine

So here is what I did,
1 Did a Rom back up from Rom manager
2 Backed up user apps with Titanium Pro
3 Updated Clock Work Mod to 2.5.1.2
4 Flashed Hboot from .79 to .92
This is were ran into a problem, after hboot flashed it just went into a boot loop were all I could do is go into hboot or clock work recovery but that is it phone would not boot. I searched a little and read that hboot wipes the kernal and that is why it will not reboot. I then went into clockwork and restored the rom I backed up in step 1, and it worked like a charm. Thought I would share so any one else who runs into this. Now off to flash cm7!

Rocking CM7 now, Thanks for all the help and advice from everyone. The Android community rocks.

Related

How do you do a nandroid backup with the Desire?

I have a rooted desire and never really tried restoring a backup and when I finally did I came across this error message:
No SD ext found. skipping backup of SD EXT
Generating MD5 sum
error while checking md5 sum!
chcking md5 sum....
MD5 mismatch!
My SD card has no partition whatsoever and I'm using fake flash by paul. My old phone was a N1 and I had no problem whatsoever doing this before. Is making a backup and restoring in the Desire an entirely different process?
Also how do you automatically backup apps in the Market? Meaning if I switch roms and just logged into my Google account the market would automatically "restore" my old apps. I used to be able to do this once in a while with my old N1 but I couldn't do it consistently. With my Desire I can't do it at all.
Thanks
It will give that error if you have no ext partition on your sd card. If you're not using apps 2 sd then you need not worry about it.
Other than that, try the latest clockwork recovery (2.0.1.4) and try a nandroid backup and restore.
Sent from my HTC Desire using XDA App
Nandroid backup seems to work and I do get to see the file but when I try to restore it fails! Do I need to make an extension for it to work?
What about restoring apps from the marketplace via the internet? Like I said, I've done it a few times with my N1 wherein it automatically restores everything once I log in my Google account.
Thanks
Try creating an ext partition, convert ext2 to ext3. If it fails again, try backing up and restoring using the Nand using the latest Clockwork Recovery (2.0.0.7).
Your apps are linked to your Google account so when you sign in, they should be available for manual download.
You could also backup and restore your apps and data to your sd card using Titanium backup or MyBackup Pro (available from the Marketplace).
Sent from my HTC Desire using XDA App
Apps are indeed linked but how do they become restored automatically? Like I said, I've done it before on my N1 with "applications restored" showing up on the notification bar.
Where do I get the latest clockwork recovery? Tried looking at the forums and came up empty. I just followed Paul's guide for rooting. Still don't understand why I can't restore from a nandroid.
thanks
I am not aware of any method to restore apps automatically from the Marketplace, i do it manually unless using a backup and restore app.
Try reading the fake flash thread on MoDaCo as i remember people had reported the same issue you are experiencing. What version of fake flash are you currently using?
You will find the Clockwork Recovery as an option in the ROM Manager app, which you can download from the Marketplace.
Sent from my HTC Desire using XDA App
kingofthebraves said:
Where do I get the latest clockwork recovery? Tried looking at the forums and came up empty. I just followed Paul's guide for rooting. Still don't understand why I can't restore from a nandroid.
Click to expand...
Click to collapse
The easiest method is to use unreEVOked (link).
The earlier version of unreEVOked installed a much earlier version of clockwork recovery, and I found that the nandroid backup didn't work properly - it would seem to backup (albeit too quickly), but you couldn't restore due to the MD5 problem. I think it didn't actually ever complete the backup and generate the MD5s.
Version 2 hopefully fixes that problem - certainly Nandroid backups take a lot longer!
Regards,
Dave
Thanks guys.
Will look into unrevoked and try to get it to work. I'll also try to update my fake flash. I have been using the very first version when it came out and never really updated it lol
Updated my fake flash and it worked! Thanks guys!
Didn't know that the clockwork recovery was embedded into fake flash. I thought it was just an enabler or something.
Thanks again!
If you use unrEVOked you don't need Fake Flash, or vice versa.
Regards,
Dave
Have still yet to try unrevoked, what exactly does it do when I plug it into my desire? Does it make me run Amon Ra's N1 recovery image? No more screen with the red triangle?
kingofthebraves said:
Have still yet to try unrevoked, what exactly does it do when I plug it into my desire? Does it make me run Amon Ra's N1 recovery image? No more screen with the red triangle?
Click to expand...
Click to collapse
No problem bud, glad it worked out for you
When you enter Recovery, it loads the recovery image straight away, so you get a permanent custom recovery image when you hold power + home.
Will try it out thanks again! Currently experimenting with the Rom manager application. It's pretty neat and u can update the recovery image instantly. I take it as something like an app inside ur phone? Always there in the background waiting to be used?
Hi, is anyone else having the problem that ClockWorkMod 2.5.0.1 just hangs after "Backing up system..." when trying to do a Nandroid backup?
Backup worked fine with 2.0.x.x (the one that came with Unrevoked3), but now I can't seem to complete a backup. Haven't even tried restoring yet...
Trying to run a ROM backup using ROM Manager and Nandriod Backup but both go to a screen with a red triangle
Phone is rooted and running Defrost
I want to update to defrost 6.1
Any other way of backing up the ROM ?
Thanks
BorgCymru said:
Trying to run a ROM backup using ROM Manager and Nandriod Backup but both go to a screen with a red triangle
Phone is rooted and running Defrost
I want to update to defrost 6.1
Any other way of backing up the ROM ?
Thanks
Click to expand...
Click to collapse
Boot in to recovery manually and back up or clear the download cache in rom manager and reflash clockworkmod. If it still fails try to disable signature verification in recovery (under install zip form sd)
I can't get to recovery though thats the problem.
How do you reflash clockworkmod ? Through ROM Manager ?
yes, first option when you open rom manager
Cashe cleared, then I tried to run the update ROM option selected back up and clear data etc.
Went straight to a red triangle, will now try and see about changing this clockworkmod
Thanks.
Ran the re-flash clockwork option, first one on the list, still gets the red triangle of noness.

titanium backup + damagecontrol 3.1.2 wont restore apps

Running DC 3.1.2 and a netarchy's 5 pt multi touch/fps fix kernel, Paid version of titanium backup.
I've fixed permissions
verified backups
installed app, apps + data, apps + system data
When i attempt to restore any app i've backed up on the sd card via titanium backup it wont restore them. It goes through, acts like it installed but when i reboot the phone and do the above mentioned things it just doesnt show up...
I should mentioned i came from stock rooted EVO 4G 1.3x ROM
Anyone ever heard of this problem before?
bump, anyone?
ANother thing its now doing is i was able to get the apps to show up in market, however they show as installed... until i click on the app then it asks me to install it.
Friggin weird.
anyone at all?
That's a weird one. I've been using Titanium quite a bit lately with no problems. You might just have to wipe and start over. Have you tried uninstalling / reinstalling Titanium? Its also possible there's a problem with your SD card. Do you have another one you could test with?
Did you go into settings / applications and put a check in the unknown sources box?
.....
Frank...
yes unknown sources is checked.
SD card as far as i know has no problems, ill try with a new one.
Thanks for the info.
im having the same problem. i have unknown sources checked, reflashed a couple times, and have even re-rooted. it works perfectly in both fresh and OMJ, but DC just fails. if you install the apps manually and then do a restore of app+data, it will restore the data properly, but it fails when you try to install from the backup.
-phil
ndboost said:
Running DC 3.1.2 and a netarchy's 5 pt multi touch/fps fix kernel, Paid version of titanium backup.
I've fixed permissions
verified backups
installed app, apps + data, apps + system data
When i attempt to restore any app i've backed up on the sd card via titanium backup it wont restore them. It goes through, acts like it installed but when i reboot the phone and do the above mentioned things it just doesnt show up...
I should mentioned i came from stock rooted EVO 4G 1.3x ROM
Anyone ever heard of this problem before?
Click to expand...
Click to collapse
Same problem here...Fresh, Calkulin's EviO, Baked Snack, and Toasted Delight ROMs have all been able to restore just fine using Titanium Backup.
It's too bad...I really wanted to try DCs ROM, but I'm not gonna go through installing all my missing apps and setting up all the screens again.
Has anyone found a way to fix this yet?
MyRCode said:
Same problem here...Fresh, Calkulin's EviO, Baked Snack, and Toasted Delight ROMs have all been able to restore just fine using Titanium Backup.
It's too bad...I really wanted to try DCs ROM, but I'm not gonna go through installing all my missing apps and setting up all the screens again.
Has anyone found a way to fix this yet?
Click to expand...
Click to collapse
Just make a nandroid backup, wipe, and try out DC 3.2.3 yourself. 99% chance everything will be fine.
cloud858rk said:
Just make a nandroid backup, wipe, and try out DC 3.2.3 yourself. 99% chance everything will be fine.
Click to expand...
Click to collapse
The problem isn't loading the ROM. I'm able to install DC after doing a full wipe...it seems to be the only ROM that causes problem when trying to do a full Titanium Backup restore.

[Q] NANDroid Backup Question...

Hey everyone... I was wondering -
If I make a NANDroid back up of my stock froyo rooted ROM (ROM #1),
Do a full wipe and then flash another ROM (ROM #2) and make a NANDroid BU of ROM #2,
Then do another full wipe and flash another ROM (ROM #3) and make a NANDroid BU of ROM #3...etc etc...
My question is - Can I restore any given NAND BU to any given ROM, or Do i actually have to reflash that ROM to get it back on the phone?
I tried doing this with a NAND BU that I made with a ROM I had flashed... it got buggy and I ended up restoring my NAND BU from the stock ROM. Then I wanted to show some one the ROM I had flashed before and tried to restore the NAND BU I made of that particular ROM and it got 3 dots into the restore then said it couldnt be completed.
I am wondering if it couldnt be completed b/c the NAND BU was corrupted some how - or if this is actually not some thing you can do...
any info on this would be helpful...
JS3
yes you can do that. before you restore you may want to wipe the cache and dalvik just to make sure that is all cleared out (unless you also do backups of the cache)
What recovery are you running when the restore failed? i am guessing amon, so when you get an error you should move the log to sd so you can check out what exactly the error was
elegantai said:
yes you can do that. before you restore you may want to wipe the cache and dalvik just to make sure that is all cleared out (unless you also do backups of the cache)
What recovery are you running when the restore failed? i am guessing amon, so when you get an error you should move the log to sd so you can check out what exactly the error was
Click to expand...
Click to collapse
Ok, I thought I could but I was thrown off by the failed attempt. I always do a FULL wipe when flashing from one ROM to another... and I'm not sure how to back up the cache...
The main back ups I preform are the NAND, Titanium and occasionally I use MyBackUpPro...but I only use the last one for contacts and texts...
I always use Amon_Ra... I am currently using 2.2.1... I am assuming that the NAND BU was corrupt some how.
I am trying to think if I made the back up with the same version of Ra or not and I assume that shouldnt make any differance. Now the only other variable would be that I changed the name of the main file - but I always do that with all my NAND BUs and I didnt have any problem restoring my stock froyo that was named in the same format...(ex: StockFroyo-011911 <~~ which worked Vs. WarmTwoPointTwo-012911 <~~ which did not work)...
You can make backups of multiple and re-flash them at your will [just know which is which, by naming them.] Also, do a cache and dalvik wipe before hand, and you're good to go.
JayStation3 said:
Hey everyone... I was wondering -
If I make a NANDroid back up of my stock froyo rooted ROM (ROM #1),
Do a full wipe and then flash another ROM (ROM #2) and make a NANDroid BU of ROM #2,
Then do another full wipe and flash another ROM (ROM #3) and make a NANDroid BU of ROM #3...etc etc...
My question is - Can I restore any given NAND BU to any given ROM, or Do i actually have to reflash that ROM to get it back on the phone?
I tried doing this with a NAND BU that I made with a ROM I had flashed... it got buggy and I ended up restoring my NAND BU from the stock ROM. Then I wanted to show some one the ROM I had flashed before and tried to restore the NAND BU I made of that particular ROM and it got 3 dots into the restore then said it couldnt be completed.
I am wondering if it couldnt be completed b/c the NAND BU was corrupted some how - or if this is actually not some thing you can do...
any info on this would be helpful...
JS3
Click to expand...
Click to collapse
Just wanted to tell ya thanks for the app recommendation (Elixir)... nvr seen it before but it's pretty awesome..
blakjak220 said:
Just wanted to tell ya thanks for the app recommendation (Elixir)... nvr seen it before but it's pretty awesome..
Click to expand...
Click to collapse
No problem, I love it... Also check out last months favorite app. I love that one too cause you can totally customize your texts and what not - It took me almost 4 hours of messing with settings to figure out EVERYTHING that handcent does...
Also thanks goes to teh, appriciate the info
That's wat I do I have several different backups of the most stable roms I like and switch to witch one I like just gota remember the date of backup
rayfrausto said:
That's wat I do I have several different backups of the most stable roms I like and switch to witch one I like just gota remember the date of backup
Click to expand...
Click to collapse
If you use rom manager, or amon ra, you can rename them, so its easy to tell.
teh roxxorz said:
If you use rom manager, or amon ra, you can rename them, so its easy to tell.
Click to expand...
Click to collapse
Yeah, I knew you could rename them... I have been doing that - but for some reason I cant get my NAND BU of myns warm twopointtwo to work, I guess I'll just reflash it... I dunno...
If your battery is less than 30%-40% or something, Amon-Ra won't restore or backup. If it's not working, plug in your phone and try again. Also, I would upgrade to RA-2.3. Much better IMO, only version since 1.8 that I haven't had any trouble with. I had also sorts of issues with backups and restores either taking FOREVER or just plain not completing. For the first time, I'm at a point where i have like 5 ROMs on my phone and switch whenever I feel like.
jstalford said:
If your battery is less than 30%-40% or something, Amon-Ra won't restore or backup. If it's not working, plug in your phone and try again. Also, I would upgrade to RA-2.3. Much better IMO, only version since 1.8 that I haven't had any trouble with. I had also sorts of issues with backups and restores either taking FOREVER or just plain not completing. For the first time, I'm at a point where i have like 5 ROMs on my phone and switch whenever I feel like.
Click to expand...
Click to collapse
Cool, yeah I may have had a bad battery level, I dont remember what my batery % was when I tried it but that makes sense... thanks, Also with the 2.3 I have it - I just havent flashed it yet... Thanks again

[Q] New EVO coming...restore nandroid??

ok so here's my situation....my EVO has a loose charging port and the power button is failing so i took it to sprint and they ordered me a new one...so i figured i would just nandroid when the new phone got here after re-rooting it and i would be good...but then i got to thinking that when i downgraded my hboot version from .97 to .76 i couldnt restore my previous backup because i switched versions...and i plan to root using the unrevoked method and i would assume they would install the lastest version of CWM witch would make my backup unusable right??...
Basically i just need to know if i would be able to restore my backup from my memory card right after i root it or if i need to jump through some hoops to do it...or if i just need to flash CM7 clean and start all over, which i would rather not do...so if anyone can give me an answer it would be much appreciated and i will give said person a kiss *muah*....hahaha
thanks in advance
I'm 99% sure that this would not work...nandroids have to be from the same phone, not just same phone specs/firmware
Even if your recovery would allow you to restore the backup, I wouldn't do it. You run the risk of restoring the wimax partition from the old phone on the new one, essentially borking your wimax. I could be wrong, though.
I would backup all of your user apps + data with Titanium Backup, skip the system stuff. Make sure you've synced everything to Google. Gather the rom you like & any addons, then run unrevoked. After it's done, flashing, restoring, and setting back up shouldn't take too long.
exactly what plainjane said!
Ok I guess I get that...but would I be able to advance restore just my data after flash my rom and kernel?...so I have my apps and data in less than 5 mins?
Sent from my nightly EVO
Vinchenzop said:
I'm 99% sure that this would not work...nandroids have to be from the same phone, not just same phone specs/firmware
Click to expand...
Click to collapse
+1 I tried restoring one of my Nandroid backups on my GFs rooted EVO....no go.
thebeast614 said:
Ok I guess I get that...but would I be able to advance restore just my data after flash my rom and kernel?...so I have my apps and data in less than 5 mins?
Sent from my nightly EVO
Click to expand...
Click to collapse
Just be careful but this should be fine. You may be better off using an app like MyBackup *root* which is free in the market to backup your apps and app data.
I have used it to move apps from rom to rom, and a new phone would be no different.
For apps...back them up via titanium backup, and you can restore them to a new/different phone
For contacts...open your contacts/people app..while looking at your contacts, press menu and choose "export to sd". This will create a file in your sd called 00001.vcf which contains your contact list and can be restored through contacts/people on any rom
Root your new phone, flash whichever rom you want...put your old sd card into your new phone...install titanium backup and reinstall your backed-up apps. Open contacts/people... press menu, import from sd card. Profit
Vinchenzop said:
For apps...back them up via titanium backup, and you can restore them to a new/different phone
For contacts...open your contacts/people app..while looking at your contacts, press menu and choose "export to sd". This will create a file in your sd called 00001.vcf which contains your contact list and can be restored through contacts/people on any rom
Root your new phone, flash whichever rom you want...put your old sd card into your new phone...install titanium backup and reinstall your backed-up apps. Open contacts/people... press menu, import from sd card. Profit
Click to expand...
Click to collapse
+1 What Vinchenzop said.

[Q] Force closes long lag times, other problems so un-root/re-root or something else?

So, I have been having some major problems with my phone. Tons of force closes, major lag times and things like that. I have tried a handful of different ROMs, including CM7, the nightlys, Miui and a few others. I hear great stories about people and rooting and I want to be one of them. I am tired of all the hassles. So, when talking to someone in the office who has had no issues with his Droid 2, he suggested, and said he has read, the best thing to do is go back to stock, unroot, as they will remove all possible conflicting files that could be causing problems. Then, re-root, and install whatever.
Any thoughts on that? Generally, my process for installing a new ROM, I boot into recovery manually, clean cache, clean Dalvik, then install ROM. Then, I restore apps and data from Titanium and restore the Nandroid from Rom Manager. The past couple times, I have done the factory reset, but eventually, a day or 2, it goes back to the same problems. Maybe, I should just try it without the restoring the Nandroid (even though it is a backup from when there was no problems) and the app data from Titanium. I assume, you know what happens when you assume, that both the Nandroid and Titanium backups are clean as I backed up when I was having no issues.
So, any thoughts here? Unroot, then re-root or is there something else I should try to wipe everything clean to solve the problems? Currently, on the original Droid Incredible (got it on the release day, so the first screen), running 2.2 when I rooted, currently on Miui 1.9.16, but just installed it 10 minutes ago and was running the Cyanogen nightly's before hand..
Thanks in advance
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
Try not restoring apps and data from Titanium, as restoring the app is okay, but restoring data can cause unwanted things to happen more times than not.
When you say restore nandroid from ROM Manager, what do you mean here? A nandroid is backing up your ROM via ROM Manager, which gets stored to your clockworkmod/backups folder...you shouldn't be pulling anything from that...
If you flash the RUU to return to stock and re-root, make sure you use the 2.2 RUU. If you use the 2.3, you need to be s-off to get rooted again. If you use the 2.3 RUU and you're s-on, no root for you...come back one year.
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
As for Titanium, I restore apps with data all the time, but system data should almost never be restored as it's OS and app version specific. Basically, if it's green, it's safe. If it's red, don't mess with it. If it's white, like a user app, app and data are usually safe to restore.
ROM Manager is a bigger pain in the ass than it's worth and is useless for anything more than flashing a new recovery. If my recovery is working reliably, I never install ROM manager. Most devs will tell you to never flash with ROM manager anyways. Any function that ROM Manager performs can be performed in recovery in a safer, more reliable fashion.
loonatik78 said:
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
As for Titanium, I restore apps with data all the time, but system data should almost never be restored as it's OS and app version specific. Basically, if it's green, it's safe. If it's red, don't mess with it. If it's white, like a user app, app and data are usually safe to restore.
ROM Manager is a bigger pain in the ass than it's worth and is useless for anything more than flashing a new recovery. If my recovery is working reliably, I never install ROM manager. Most devs will tell you to never flash with ROM manager anyways. Any function that ROM Manager performs can be performed in recovery in a safer, more reliable fashion.
Click to expand...
Click to collapse
Thanks for the correction, I forgot to put system in there...restoring system data is not good.
+1 on ROM Manager issues, always get a zip file of the ROM, and flash through recovery.
RMarkwald said:
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
When you say restore nandroid from ROM Manager, what do you mean here? A nandroid is backing up your ROM via ROM Manager, which gets stored to your clockworkmod/backups folder...you shouldn't be pulling anything from that....
Click to expand...
Click to collapse
That is pretty much what I do, except for the Mounts and Storage parts.
For the Nandroid part, maybe I have my terminology mixed up. I do a restore from Rom Manager...which I thought was called the Nandroid backup. It seems to me, that it makes sure the launcher and things are set up right.
loonatik78 said:
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
Click to expand...
Click to collapse
I rarely use the ROM Manager to do anything, just restore (what I thought was called the Nandroid) to make the launcher the way things were..
But it seems like that is my problem. I am installed the new ROM, then just restoring a back up of all the problems. DUH.. Guess I should try it all without restoring anything from the ROM Manager and see how it all works. That will be my project tonight..
Thanks
MikeDaub said:
That is pretty much what I do, except for the Mounts and Storage parts.
For the Nandroid part, maybe I have my terminology mixed up. I do a restore from Rom Manager...which I thought was called the Nandroid backup. It seems to me, that it makes sure the launcher and things are set up right.
I rarely use the ROM Manager to do anything, just restore (what I thought was called the Nandroid) to make the launcher the way things were..
But it seems like that is my problem. I am installed the new ROM, then just restoring a back up of all the problems. DUH.. Guess I should try it all without restoring anything from the ROM Manager and see how it all works. That will be my project tonight..
Thanks
Click to expand...
Click to collapse
If you want to restore your launcher, try it through Titanium Backup. If that doesn't do it, and I can't promise you it will work correctly, you're probably SOL on restoring a launcher unless some other backup app does the job better.
loonatik78 said:
If you want to restore your launcher, try it through Titanium Backup. If that doesn't do it, and I can't promise you it will work correctly, you're probably SOL on restoring a launcher unless some other backup app does the job better.
Click to expand...
Click to collapse
I am fine with not restoring it, I just thought "that is what you should do".
I don't venture too far from the regular settings, so it isn't a pain to do, just thought I should...
RMarkwald said:
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
Click to expand...
Click to collapse
One more quick question since I am thinking of it....is this same process if doing nightly updates from Cyanogen, or just is I change from say, Cyanogen to Miui or something??
Thanks again for all the help..
MikeDaub said:
One more quick question since I am thinking of it....is this same process if doing nightly updates from Cyanogen, or just is I change from say, Cyanogen to Miui or something??
Thanks again for all the help..
Click to expand...
Click to collapse
Generally, CM nightlies can be flashed over top of each other without a wipe since the vast majority of the code is identical. However, if an issue crops up, a wipe and flash might be a good thing to try. Probably won't help though, since nightlies, by definition, are experimental.
Always wipe and flash when moving from one ROM type to another.
loonatik78 said:
Generally, CM nightlies can be flashed over top of each other without a wipe since the vast majority of the code is identical. However, if an issue crops up, a wipe and flash might be a good thing to try. Probably won't help though, since nightlies, by definition, are experimental.
Always wipe and flash when moving from one ROM type to another.
Click to expand...
Click to collapse
That's kinda what I figured, but I thought it was worth asking so I don't completely wipe the whole thing every time I install an update. The nightly I am on now seems to be working, so the new plan is keep whats working until it doesn't work anymore, or some major update comes along..
Thanks again for the help. I really appreciate it.
If the issue continues you can try copying everything off of your SD card to your PC and reformatting your SD card. Remember to use FAT32 format. Then copy everything back to your SD card. I've read threads were this helped the force close issues for many people - Just a thought.
jackbtha1 said:
If the issue continues you can try copying everything off of your SD card to your PC and reformatting your SD card. Remember to use FAT32 format. Then copy everything back to your SD card. I've read threads were this helped the force close issues for many people - Just a thought.
Click to expand...
Click to collapse
Certainly worth a thought. The card that is in it now came from a different phone. I am pretty sure I formatted it when I first plugged it in, but it can't hurt to try...
Thanks

Categories

Resources