Oh what up all,
So recently I tried putting Fission 2.whateverthenewoneis Froyo on my D2g. Did a nandroid backup, installed the rom.
The only problem I had was that Fission wouldn't take me out of airplane mode. Go figure. So, I freaked, no idea what to do, and just decided I'd roll out with my nandroid backup. So now I'm back to stock, and my phone is working just as it should. So I guess my question is this:
Does every nandroid backup put you back in that exact position you were in when you made the backup? Or am I still somehow in some weird mixed version between Fission & Stock? Like a smoothie?
Also, does anybody else have the airplane mode problem with Fission? I'm thinking maybe black edition might give me better results, but probably not.
Stay Easy
WhatupMike said:
Does every nandroid backup put you back in that exact position you were in when you made the backup? Or am I still somehow in some weird mixed version between Fission & Stock? Like a smoothie?
Click to expand...
Click to collapse
Every nandroid backup saves everything when you back up so there shouldn't be any mixing. The only thing that might be held over are miscellaneous files in the cache but you can wipe cache without wiping data and be fine, or not wipe at all cache won't hurt anything.
Also, if you are having issues with the D2G version of fission try posting in their D2G release thread to let them know about any issues.
Related
I've tried more than twice now, and I'm sure it's something simple, but I can't recover my backup. Last night for example, wanted to try another rom, a 2.3.4, I was quite happy with my mosaic setup, as usual, and I was running xcal's 2.0 kernel without issue so I backed up through cwm 3. Flash got me into a bootloop so I tried to recover the nandroid but it wasn't the right one. I chose the right date but the b/u was the rom that failed, the bootup screen. So I had to start from scratch to get the setup I liked. Of course when I tried to flash the new rom there were different kernels etc. But that shouldn't matter should it. What am I doing wrong? Thanks ahead of time.
Sent from the frozen tundra known as Canada.
Do you're trying to restore a 2.3.3 backup (Mosaic) to a 2.3.4 rom?
*phone sig* If you're not on Gingerbread you should be flogged! *
Uh, no. you misunderstood.
Sent from the frozen tundra known as Canada.
Those back ups are not to use to recover with. Those are to restore your set up and stuff, you flash the rom it was backed up from THEN restore and its like you never flashed the the other rom.
studacris said:
Those back ups are not to use to recover with. Those are to restore your set up and stuff, you flash the rom it was backed up from THEN restore and its like you never flashed the the other rom.
Click to expand...
Click to collapse
Thanks studacris, yeah, tried that and got an error message and couldn't restore. Sorry I didn't take the message down, I'll try again if it happens again, thanks.
Sent from the frozen tundra known as Canada.
When I switched between my nandroid backups (all stock 2.1), then how come I dont have to factory reset after restoring that back up?(unlike when switching to dexter's rom I need to factory reset) anyone care to explain?? Any help would be appreciated!!
Sent from my Milestone XT720 using XDA App
At least from my point of view, it's easier to tell people to factory reset than to hunt down and fix obscure problems. One of the first troubleshooting steps will probably be factory reset anyway. My feeling is more advanced users figure out their own thing. I used to post elaborate instructions, but more possibilities/options just confuses the least experienced users. It saves a lot of hassle to just post the single most sure-fire set of instructions and then help people that want to try different things later. At least that is my current philosophy.
Sent from my Milestone XT720 using XDA Premium App
When you factory reset with our custom Roms it isn't like when you do it on a stock phone and you get the green Android welcome screen. The long and short of it, as I have read, is that if you created the nandroid, ie backup, you wont need to do the factory reset, just wipe dex and cache partitions. If you are moving between "fresh" Roms like from Dexter or Khals to Miui, then I would do it for sure to make sure you have a clean slate to start your modding. But I agree with Mio, number one thing I do when I have an issue is do a factory reset and move from there.
Woodrube said:
When you factory reset with our custom Roms it isn't like when you do it on a stock phone and you get the green Android welcome screen. The long and short of it, as I have read, is that if you created the nandroid, ie backup, you wont need to do the factory reset, just wipe dex and cache partitions. If you are moving between "fresh" Roms like from Dexter or Khals to Miui, then I would do it for sure to make sure you have a clean slate to start your modding. But I agree with Mio, number one thing I do when I have an issue is do a factory reset and move from there.
Click to expand...
Click to collapse
So if i want to switch from my dexter 2.2 rom to my 2.1 nandroid backup, i have factory reset?
I think that if you are only switching from back ups that you already made, you don't have to, but I wipe dex, cache partitions and factory reset everytime. Like I said above, it is always good to have a clean slate to start off with. From what I have gathered, it doesn't wipe everything clean, it wipes everything clean back to your back up point. In my experience, everything will still be there (except for a few passwords), there being the point that you made a back up. Oh also forgot about this key factor. When I back up, I do the top 5 and maybe the sd-ext depending on if I have purchased anything new. Loosely think of it as a restore point in Windows. The reset will only reset to the data backup that you made, nothing beyond or before.
androidlover123 said:
So if i want to switch from my dexter 2.2 rom to my 2.1 nandroid backup, i have factory reset?
Click to expand...
Click to collapse
I'm not so sure about that. I can imagine Android has features to upgrade things like sqlite databases forward from 2.1 to 2.2, but I doubt 2.1 knows how to downgrade from 2.2. For jumping between OS releases, I'd use something like Titanium Backup to copy apps and preferences. But moving laterally i.e. 2.2 to 2.2 or 2.1 to 2.1 it's more likely to be ok.
So my stock Infuse 4G is now Infused 2.1 and I LOVE it. So happy with the change. With that said, what is the number one BEST option to backup the phone in case I do anything stupid? I'm usually very thorough but sometimes I act too quickly.
I'm assuming booting in Recovery and doing the backup there is a good step, is there anything better? Never used Titanium but I see it mentioned a good deal but it seems that you can use it for some things yet not others. I just want a verified safe and secure method.
Also, another question if I may. Since I didn't do any type of backup to begin with, is it safe to assume I can't get back to Froyo at this point? Not that I really want to but I'd like to know either way.
Thanks!
Kadin said:
So my stock Infuse 4G is now Infused 2.1 and I LOVE it. So happy with the change. With that said, what is the number one BEST option to backup the phone in case I do anything stupid? I'm usually very thorough but sometimes I act too quickly.
I'm assuming booting in Recovery and doing the backup there is a good step, is there anything better? Never used Titanium but I see it mentioned a good deal but it seems that you can use it for some things yet not others. I just want a verified safe and secure method.
Also, another question if I may. Since I didn't do any type of backup to begin with, is it safe to assume I can't get back to Froyo at this point? Not that I really want to but I'd like to know either way.
Thanks!
Click to expand...
Click to collapse
You can get back to Froyo but not without wiping your data.
Nandroid backups (from Recovery) can restore your phone to an EXACT state - apps, data, and ROM.
TiBu is fairly flexible and, for example, can take all of your installed apps, back them up along with their data, and restore the missing apps when you switch ROMs. (Be EXTREMELY careful restoring system data or data for non-missing apps - 90% of the time it will break.)
I use Call Logs Backup and Restore and SMS Backup and Restore to back up what TiBu can't
Ok so if I simply want to make one big global backup, the Nandroid backup is a good way to go? I'm not too concerned with backing up stuff individually, more of a 'once a month' type of backup so if something disastrous happens, I can get back to a working state.
Also, if I were to do something that maybe caused a boot loop or some other type of bricked scenario, what is the process for restoring the backup? As in, how do you get back into the Recovery option if you can't boot into the OS to begin with?
Kadin said:
Ok so if I simply want to make one big global backup, the Nandroid backup is a good way to go? I'm not too concerned with backing up stuff individually, more of a 'once a month' type of backup so if something disastrous happens, I can get back to a working state.
Also, if I were to do something that maybe caused a boot loop or some other type of bricked scenario, what is the process for restoring the backup? As in, how do you get back into the Recovery option if you can't boot into the OS to begin with?
Click to expand...
Click to collapse
For that, you have the Ultimate brick solution though I've never had the need to try it.
I've been switching roms quite a bit lately. For each and everytime I :
(1) Do a Tibu backup of all system and apps
(2) Do a Nandroid backup (either from red cwm or from ROM mgr)
The Tibu is the logical backup while the Nandroid is the physical image backup.
So far, I've gone to Serendipity (too many issues) back to my trusted 1.6 without much effort. The Nandroid restore is initially not 100%, some of my shortcuts like gosms and my unlocker setup was messed up. But then I'll go into Tibu, check to see what apps are missing and just restore those. In my case, after restoring gosms and reboot, all is good. I think the apps that have a system equivalent, will need to be restored individually.
However, that said, I haven't been too successful with Tibu on restoring *all* apps installed under Froyo (Infused 1.6) to GB (S7). This is even with the pro's automated method. This is likely so because those apps don't work well with GB and nothing to do with Tibu.
I've been using Titanium Backup for over a year. Third different phone, and maybe 30 different ROM's. I've never had a problem what so ever. Just remember rule #1, when switching ROM's with TitBU... restore "missing apps and data" ONLY! And you'll be fine.
Jep56 said:
I've been using Titanium Backup for over a year. Third different phone, and maybe 30 different ROM's. I've never had a problem what so ever. Just remember rule #1, when switching ROM's with TitBU... restore "missing apps and data" ONLY! And you'll be fine.
Click to expand...
Click to collapse
+1
I second this. Moved between multiple phones, and hard-to-count number of roms, and TiBu was always there to help me out
Please Help,
For some reason everytime I try to use CWM to restore a backup, I always get a boot loop. The first time it happened to me was because I was on Infused(GB) and tried to restore back to Infused(froyo). Atleast, after doing some reading that was what I thought caused it anyway.
Yesterday I was on Infused 2.2.1. I then made a backup. Next I flashed to 2.2.2. I Then decided to go back to 2.2.1 by restoring the backup I just made. I was then in a boot loop. I had to go back to stock and start over.
I am now on Infused 2.2.2. My phone is working really great at the moment. Everyone was complaining about inaccurate GPS. Mine is locking in 5 seconds and accuracy of 5 to 6 meters all the time!!
Ok, The point of all of this is. I want to make a reliable backup of my phone in the state it is in right now.
Am I doing something wrong when I try to restore from a backup? I always wipe cache partition and wipe dalvik cache and then restrore then reboot.
Any help on this would be greatly appreciated!!
Move between same version of android, not different versions.
Say, u r on 2.2.2 now, and then u go to Froyo. If u want to get back, do a clean install of 2.2.2 and then go to recovery and restore
diablo009 said:
Move between same version of android, not different versions.
Say, u r on 2.2.2 now, and then u go to Froyo. If u want to get back, do a clean install of 2.2.2 and then go to recovery and restore
Click to expand...
Click to collapse
I am pretty sure that's what happened to me the first time.
I just cant explain the second time. 2.2.1, make backup, flash to 2.2.2. then restore back to 2.2.1....boot loop.
I'm starting to wonder if nandroid backups in CWM are broken for us... I haven't had a chance to really test it myself but this isn't the first time I've seen reports of the problem.
Entropy512 said:
I'm starting to wonder if nandroid backups in CWM are broken for us... I haven't had a chance to really test it myself but this isn't the first time I've seen reports of the problem.
Click to expand...
Click to collapse
Is there any other way I can I make a reliable backup that you know of?
Edmlaser said:
Is there any other way I can I make a reliable backup that you know of?
Click to expand...
Click to collapse
Any time I move between roms, I make a clean install of the rom, and restore the backup of the same rom, clear dalvik cache and cache and reboot. I know its a lil roundabout process, but it works.
diablo009 said:
Any time I move between roms, I make a clean install of the rom, and restore the backup of the same rom, clear dalvik cache and cache and reboot. I know its a lil roundabout process, but it works.
Click to expand...
Click to collapse
Ok. I will try this next time I need to restore.
Thanks for taking the time to try and help me out.
So right now I'm using CWM to do my nandroid backups. I make one after I make any major updates or changes - call me a worry wort. I also use Titanium Backup.
With doing this, obviously it takes up a bit of room so I offload them to my computer. The issue here is if I do something detrimental and need to restore, I don't know of a way to get the backup files back onto the internal memory since you can't access them via CWM, if that makes sense.
I guess I can simply keep just the latest backup saved on the phone itself but I'm wondering if there's another method that I'm not aware of. Is there a way to get files copied to the internal memory if you can't fully boot into the OS?
Oh and one other question: Does a nandroid backup include every single item? Basically is it a 100% clone of the device or are some thing left out? Basically if I tried a completely different rom and then decided to go back to an entirely different rom, would I simply be able to restore it and be up and running? The last restore I did seems to indicate it does but that was going from different versions of the same rom.
nandroid is a clone of ur system.
diablo009 said:
nandroid is a clone of ur system.
Click to expand...
Click to collapse
Ok that's what I figured; read something a bit ago which seemed to say something else.
So if I want to test a few completely different rom setups and make a nandroid backup of each one, I could essentially swap between them whenever I want by simply restoring them and I'll get back to the exact state as I was at the time they were made? Menus and all?
So apparently a kernel change will not get reverted via nandroid. Anything else? Just tried Entropy's daily driver and apparently it's a no go for me. Restored via nandroid and still freezes during 'X' boot animation.
I was running Infusion 1.1 and made sure to reset the VC O/C back to stock and reboot before updating...