Related
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
I am having a problem with switching ROMs on my sensation which just started a few days ago. I am currently running ARHD 3.1.1 and it is very stable and I have had no problems whatsoever, but like many here, I like trying out different and new ROMs. Anyways, I did a backup and installed ARHD 3.6.2, and it was forcing close on several apps, and kept getting soft reboots, so I tried RCMix's, and it would load and automatically install some apps and settings that I had on my previous ROM, and it was working fine, but then I started getting soft reboots when I would open any app, so I tried about 2 other ROMs (S3n5eay/Pyramid3D) and same thing, so being fed up I restored my backup and then I began to have superuser problems, so I unistalled updates, cleared data, and still was unable to gain root access. I kept clearing data, installed superuser 2.3.6 then 3.02 and finally got root again, but everytime I reboot I lose root. I then again tried different ROMs, and same thing is happening. I have used superwipe script, ARHD's wipe script, P3D wipe script, formated from CWM, and no matter what, I am still unable to keep a new ROM and keep losing root with my backup. I'm sorry for a long post, but can anyone please help me figure this out. I have upgraded ROMs many a times in the past on this phone and others, and have never experienced these problems, so can someone please help me.
I kinda had the same problem with you, with that being root was the problem. But the ROM's are pre-rooted so that shouldn't be a problem. Try to flash the root file again, until it is succesfull flashed.
Thanks. I'll go ahead and try that.
Sent from Sensational toy running ARHD 3.1.1
Geez, that sounds horrible, man. It never ceases to surprise me how different every one of these seemingly identical devices are.
West0000 said:
Geez, that sounds horrible, man. It never ceases to surprise me how different every one of these seemingly identical devices are.
Click to expand...
Click to collapse
Well for the most part everyone downloads different software. For that just one of the factors that make us all somewhat "different" this is why everyone has some sort of problems here and there.
Most times a fix can be a reboot or reinstall of the app. Even clearing of caches helps because of data conflicts on the phone. Especially when someone like me that flashes different ROMS, that's why nandroids and backups are key so that if you fudge up your phone, you can always revert back to your nandroid.
And for all the people who are trying to revert back to their nandroid after flashing a different rom, you need to use the wipe data scripts in ARHD or Coredroid to reformat the ext4 before reverting your nandroid. Just a FYI.
All I know is that wiping everything before flashing a new ROM does not guarantee that you won't get FCs and soft reboots.
For example, I did a factory reset, wiped cache, wiped dalvik, and then did superwipe (yes I know redundant), and then flashed a ROM and I thought nothing could go wrong. Then while setting up I went ahead and setup my google account during the setup process, and once I was finished I began restoring my apps+data from Titanium Backup. While that was happening Market started auto-reinstalling my apps, and this instantly conflicted with the fact that I was doing the same thing from TB. It caused a few of my apps to FC all the time. So make sure you skip adding your google account during setup.
You can also get stuff to go haywire if you restore system data from TB. Doing so will conflict with the ROM and cause FCs and reboots. For example, I didn't know how to easily back up texts and contacts for a while, and I would go in to TB and restore everything that said something like mms, messages, texts, messages widget, etc. and doing so actually caused my messages to go haywire. Same thing with contacts. The only things you should be restoring from TB are your user apps+data. As already noted, you should also superwipe before restoring a nandroid because it is exactly like flashing a new ROM. If you're on a ROM you just flashed that has 1 version of superuser, and then you go straight into recovery and restore a nandroid without wiping everything first (and has a different version of superuser), you're going to get issues with superuser.
The rule of thumb when it comes to avoiding FCs and reboots is to avoid letting data conflict. Don't mix ROM data, don't mix app data, don't restore system settings from your old ROM on your new one, etc.
Believe me, I have attempted everything without any success. I guess I'm going to stay on my current ROM until I get the time to deal with all of this, and hoping that for whatever reason I don't have to reboot my phone, or that it randomly reboots in order not to deal with the problems. I have always wiped going/coming from different ROMs, but have never experienced this before, and it is very frustrating especially when I like to try different developers mods. I'll keep attempting to try to figure this out, and if I find a solution, I will update.
cbrvnm said:
Believe me, I have attempted everything without any success. I guess I'm going to stay on my current ROM until I get the time to deal with all of this, and hoping that for whatever reason I don't have to reboot my phone, or that it randomly reboots in order not to deal with the problems. I have always wiped going/coming from different ROMs, but have never experienced this before, and it is very frustrating especially when I like to try different developers mods. I'll keep attempting to try to figure this out, and if I find a solution, I will update.
Click to expand...
Click to collapse
Keep trying different ROMs and different strategies of when you wipe/restore stuff. It's quite interesting that theoretically identical phones can have different responses to the exact same actions. 2 people can install a ROM in the exact same way and for 1 it will work, the other it won't. You just gotta work it out until you figure out how to manage your particular issues.
Yeah, I hear you. It's just very frustrating when in the past I have switched ROMs on all the phones that I have ever owned without any problems until now. But I'll try different methods and see what happens. I appreciate everyones input. Thanks. Oh, and if anybody has any other suggestions, please, share.
Ok, I was able to get Pyramid3D v0.8.0 working so far. I flashed with superwipe about 3 times then installed the ROM. I did not sign into my account, and installed my apps from titanium first, and then signed in. I got several reboots with setcpu so I unistalled it. I also get a few market fcs. Now the problem that I have is that I installed the 4EXT recovery and my phone is unable to play my music files through any of the music players. I am able to open them with astro, but not music player. But I guess I'll try to figure this one out now. Thanks for the advice.
The Janitor Mop said:
All I know is that wiping everything before flashing a new ROM does not guarantee that you won't get FCs and soft reboots.
For example, I did a factory reset, wiped cache, wiped dalvik, and then did superwipe (yes I know redundant), and then flashed a ROM and I thought nothing could go wrong. Then while setting up I went ahead and setup my google account during the setup process, and once I was finished I began restoring my apps+data from Titanium Backup. While that was happening Market started auto-reinstalling my apps, and this instantly conflicted with the fact that I was doing the same thing from TB. It caused a few of my apps to FC all the time. So make sure you skip adding your google account during setup.
You can also get stuff to go haywire if you restore system data from TB. Doing so will conflict with the ROM and cause FCs and reboots. For example, I didn't know how to easily back up texts and contacts for a while, and I would go in to TB and restore everything that said something like mms, messages, texts, messages widget, etc. and doing so actually caused my messages to go haywire. Same thing with contacts. The only things you should be restoring from TB are your user apps+data. As already noted, you should also superwipe before restoring a nandroid because it is exactly like flashing a new ROM. If you're on a ROM you just flashed that has 1 version of superuser, and then you go straight into recovery and restore a nandroid without wiping everything first (and has a different version of superuser), you're going to get issues with superuser.
The rule of thumb when it comes to avoiding FCs and reboots is to avoid letting data conflict. Don't mix ROM data, don't mix app data, don't restore system settings from your old ROM on your new one, etc.
Click to expand...
Click to collapse
Good post. I didn't realize I should be doing so much wiping even before restoring a backup.
Incidentally, I'm kicking myself now, but in the excitement of flashing my first custom ROM, I forgot to backup my original system. Doh. It's the only time I haven't backed up before changing ROMs, but that's arguably the most important backup to make.
I followed the instructions exactly on this page: http://forum.xda-developers.com/showthread.php?t=1663169
CM9 seemed to work fine for a while. I installed Titanium Backup and brought back my apps and just a bit of system data (contacts, voicemail, texts, etc). After I had restored those things, it said it suggested a reboot. I did that, but now it just reboots over and over. I can't get in to the OS for more than a few seconds before it reboots again. Help please!
As that thread specifies, I have a MX2 from CSpire. For now I don't care so much about getting CM9 working as just getting my phone back to a working state. I have both a nandroid and titanium backup on the sd card. I just need very specific instructions on how to get back to the way it was (2.3.6) given that I can't get in to the OS.
Edit: Pulling the battery doesn't resolve anything
Does it let you stay in long enough to remove the app/settings you restored? Are you able to get into recovery mode at all?
If you can get into recovery you might first want to try Fix Permissions and see how that works. If this does not solve it then consider doing a factory wipe and start restoring your apps/settings again one by one and rebooting in between until you get to the particular one that started your reboot problem.
What ROM were you on prior to CM9? Although they should be largely universal sometimes there are some slight changes in custom ROMs that might work well in many other ROMs but not in a select few. Other times it is an app that is not compatible.
The post below might be of some help since your phone seems to have a different method of getting into recovery than what I have dealt with so far.
http://forum.xda-developers.com/member.php?u=4395758
Factory Restore DX2
This might help. It's a factory restore, like you just bought it. http://forum.xda-developers.com/showthread.php?t=1317707
After much sweat, tears, and button pressing, I have gotten it back to stock CM9 and it seems to be behaving as expected. I am going to install apps one by one and reboot between every install. Hopefully I'll find the culprit soon enough.
I've got back to stock-rom with my XT1068, and it took me a lot of time to configere my Phone and apps to my desired settings. After this I've made an backup using TWRP. I've choosen to let TWRP compress this backup to save some storage space, and it was completed without anny errors. So I guess the backup is valid...
Now I wanted to go back to my clean configuration. So I've wiped my Phone using also TWRP, and tried to restore the backup after this. But I'm stuck at this point unfortunately.
It fails somehow. It seems that I can restore all the selectable options, except the data part. When restarting the Phone, it starts a new configuration (like starting the Phone from scratch and for the first time). But without anny personal settings or installed apps. When I've trie to restore data after this, it still fails.
After trying a lot of diffrent things, I only once manged to get a restore from the backup, so I guess this backup is not corrupted.
Someone maybe knows how to solve this? Manny thanks in advance!
Hi guys, wasn't sure where to post this and I've been searching the web for hours without coming up with an answer with the best way to fix the problem I've got.
So yesterday my sister gave me her phone saying it was shat and slow and generally rubbish (S4 i9505 running 4.4.2). So I had a brief look at it and she had absolutely no room on the phone at all, it was completely clogged. So I deleted all the cache data (4 gigs!!), as soon as I did this the phone came back to life and started updating everything it could, then made a backup in CWM. Thought while I'm here I may as well put the official Lollipop firmware on it from Sammobile. All was good until I realised that she has never backed anything up to google or any other cloud storage (pretty dumb!) and all of her important stuff I couldn't get back.
So I then had to try and extract some data from the CWM backup... couldn't do it. I just couldn't find the files that she wanted restored. Mainly whatsapp messages and pictures and also Smemo. These are all she needs, there's really important memos apparently, why the hell she never backed them up or had another copy of them is beyond me if they were that important!
So I tried restoring just the data part of the 4.4 CWM restore to the 5.0 rom, looking back now I see this is where I went wrong and was asking for trouble.
So I then tried rolling back to the full CWM backup, all went well so I assumed and it said it was successful. This was until the phone booted. Constant spamming of gapps has stopped working, and no matter what I did I couldn't get it to stop, the phone was unusable with it constantly pinging up, every app was failing, and then it would turn itself off and reboot.
So I Factory reset again and wiped everything, installed the backup again, same thing happened again. Even tried flashing the latest version of gapps, but nothing had any effect.
So now I'm thinking oh feck... I didn't make a backup of the Lollipop install as I thought the rollback would have just cured it, and she had already started messing about with it, making it look pretty and getting people to send her some of the important files she had.
So I thought balls, tough luck and you'll have to start again, your fault for never backing anything up. So I reflashed Lollipop, and for some reason it wouldn't boot. Would just hang at the Samsung logo, this was 4am, I was panicking as I'd effectively bricked her phone. So after lots of boot loops and countless flashes I was looking on ebay for a new phone for her, then suddenly it finally boots on one of the flashes.
Anyway after a lot of faffing about, flashing 4.4 which worked, so flashed 5.0 again, and luckily it booted, I don't know what happened, maybe I missed something as I was so tired, so I signed her into google and let all the apps download while I slept.
Now the question is, I seem to have found a site that explains how to extract individual files vaguely, I just need to get the smemos and whatsapp files and I'm not entirely sure where to look and extract these files. Also, will they corrupt if I try to install them on the 5.0 firmware?
Any help would be much appreciated as I'm really in the stinky brown stuff.
Morning bump if anyone can shed some light on this :crying:
Hi
Thanks for writing to us at XDA Assist. Have you tried using this tool?
[Tool] Cwm nandbackup file Extractor ( .img/ .tar files )
It should extract exactly what you need. If you're only reinstalling those specific apps with their data you should have no issues, just don't restore any system data, that's what caused your problems after restoring the KitKat backup on top of the Lollipop ROM.
No response in two days, thread closed, thanks.