Related
As posted in the gummy thread, I am experiencing my home button not functioning. Good news i narrowed it down. My roms are good and when fresh the home button operates normally. I have been up and down flashing left and right between GB and Froyo and the roms that overlay them. Titanium backup is the issue, or rather me backing up. yesterday I flashed to EE4 Eclipse pbj coming from GB NAMELESS Eclipse. I restored and that's where the problem showed. My dock went to just applications and none of my buttons worked except for holding power button. I booted to CWM and cleaned cache and wiped, i was left with a working fresh rom.... So now i have the same problem again when restored system i lost my home button, I filtered the restoration files too, only did contacts,mms and things along that line... My question what is the bad restore that i'm doing and how can i fix my current bad restore without losing everything?
thanks Jeff
I noticed that issue with earlier versions of nameless. perhaps it is something with that.
Sent from my SCH-I510 using Tapatalk
although currently i'm not running nameless maybe it autobackuped up part of the system when NAMELESS was on my device. Restoring must change a file that isn't compatible with other kernels. If only i could pinpoint the restoration file that does it and get a fake file to replace it
So randomly after 2 manual starts I lost all the launcher icons and no longer have a lock screen. This occurred after I installed a boot animation app. changed my logo, execpt I restarted once and everything was intact. The second restart was where problems arises. Tomorrow im wiping and restoring apps only. Thanks for the help nitro
Sent from my SCH-I510 using XDA App
Simple solution. Don't restore system data. Restoring system data can play havoc with your device when coming from and to different roms. Think about it, some of those system settings you are trying to restore might not even exist on another rom. Stick to restoring user apps, and select user app data, and then get practiced in redoing system settings after a wipe. You'll get used to it doing this over and over. It takes me only 20-30 minutes to go from completely wiped back to my usual setup.
Remember, when restoring data, less is more.
Yep thays what I was thinking. Purchased titanium pro now im back after factory reset not flash
tcollum said:
Simple solution. Don't restore system data. Restoring system data can play havoc with your device when coming from and to different roms. Think about it, some of those system settings you are trying to restore might not even exist on another rom. Stick to restoring user apps, and select user app data, and then get practiced in redoing system settings after a wipe. You'll get used to it doing this over and over. It takes me only 20-30 minutes to go from completely wiped back to my usual setup.
Remember, when restoring data, less is more.
Click to expand...
Click to collapse
Sent from my SCH-I510 using XDA App
I know there are a lot of questions about this on XDA, but no one seems to give a straight answer on how to fix this or even prevent it.
I flashed kh2 deodexed today via CWM, everything went fine.. I installed titanium backup to restore my apps, which I did, they worked fine until I rebooted the phone. Then the apps dissapeared, and the home screen shortcuts display the SD card icon and they won't open "Application is not installed on your phone".
Then, I did a wipe to data and cache partitions, but this time I restored apps only (without data) one by one, as I needed. Not as a batch, as I did last time, and was working ok. Though, I thought I'd try the ICBINB kh2 ROM, so I flashed it fine. Restored apps through titanium backup, this time one by one, mostly apps only (some of them w/ data) and was working fine, but suddenly the apps dissapeared again.
I'm about to wipe the phone to fix this... but, is there a way to prevent this from happening again?
Is restoring data from titanium causing this?
Well there has been many direct answers on this topic. Factory reset. restore from cwm, not TB.
Sent from my SGH-T959V using xda premium
hey, didn't know that. **presses thanks button**
I just restored apps via cwm, fixed permissions and it's working. It even got my settings back.. wtf. I was living under a rock all this time.
But is it completely safe? I guess that for GB builds, doing backups and restoring this way may be harmless, but probably not the same story if coming from a froyo rom.
Anyway, thanks a lot.
yea, what i did was flash both 2.2.1 and 2.3+ fresh. then backup each and whatever rom you go to, flash the corresponding backup.
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 have a Verizon Galaxy Nexus (rooted stock 4.0.4). I decided I would test out Clockworkmod touch recovery before doing anything too serious with it. So, I made a backup, rebooted, deleted an app, went back to recovery, and restored my backup. But, while it was restoring my data, it suddenly stopped and said "Error while restoring /data!" I rebooted and, after waiting through a really long boot, it booted into a semi-reset version of my phone. All of the apps claim to be installed but will not start.
So, thinking it could be a touch recovery issue, I flashed an older version of clockworkmod recovery and tried restoring after clearing my data, cache, factory reset, and Dalvik cache. Still, the exact same thing happened. I also tried restoring older backups, but the exact same thing happened.
What is going on, and what should I do? Thank you for your time.
Eric_Eric_Eric said:
I have a Verizon Galaxy Nexus (rooted stock 4.0.4). I decided I would test out Clockworkmod touch recovery before doing anything too serious with it. So, I made a backup, rebooted, deleted an app, went back to recovery, and restored my backup. But, while it was restoring my data, it suddenly stopped and said "Error while restoring /data!" I rebooted and, after waiting through a really long boot, it booted into a semi-reset version of my phone. All of the apps claim to be installed but will not start.
So, thinking it could be a touch recovery issue, I flashed an older version of clockworkmod recovery and tried restoring after clearing my data, cache, factory reset, and Dalvik cache. Still, the exact same thing happened. I also tried restoring older backups, but the exact same thing happened.
What is going on, and what should I do? Thank you for your time.
Click to expand...
Click to collapse
There may have been a corruption in your data backup. Just delete that backup and make a new one.
Nope, I tried all three of my backups and had the same problem with all three. Plus, I can't simply make a new backup. I tried restoring to the backup and lost my stuff because it didn't finish restoring my data.
I'm having some issues with cwm too. Sometimes when I'm trying toi recover, it says "md5 mismatch", maybe its a linked problem?
Sent from my GT-S5830 using XDA
rommanager
Install rommanager.apk premium and, to me is to solve the problem
So, I think I figured it out. Apparently, I only get this error when my backup contains more than a certain number of apps (or possibly the /data is over a certain size). Granted, I do have over 350 apps, but why is CWM Recovery messing up while trying to restore a big backup? It really should not affect it, but it seems to. So, I will be backing up with Titanium for my apps, and making nandroid backups only when I have under about 350 apps installed. If anybody else has any insight, please share it with me. Thanks.
The Answer (I am pretty sure...)
Okay, I think I finally figured it out. The reason it was not restoring properly was because I had about 350 user apps installed. My guess is that, while restoring, the recovery (CWM recovery in my case) puts the /data onto the RAM, and the RAM is not large enough to hold that much at once. I deleted a lot of apps, backed up in CWM recovery, and restored back to the backup, and everything worked flawlessly. I am surprised that no one has ever had this problem. So, in the future, I am making Titanium backups of all my apps, batch uninstalling a bunch of them from within Titanium (so that I have under 300 at the most), and then making a backup. Then, I can flash a new ROM, recover, or whatever and finally use Titanium to put all my apps and data back. I just thought I would post this in case anyone else ever finds this problem. It was really frustrating for me, but the insufficient RAM theory seems to explain it. Post your thoughts on the matter.
Eric_Eric_Eric said:
I have a Verizon Galaxy Nexus (rooted stock 4.0.4). I decided I would test out Clockworkmod touch recovery before doing anything too serious with it. So, I made a backup, rebooted, deleted an app, went back to recovery, and restored my backup. But, while it was restoring my data, it suddenly stopped and said "Error while restoring /data!" I rebooted and, after waiting through a really long boot, it booted into a semi-reset version of my phone. All of the apps claim to be installed but will not start.
So, thinking it could be a touch recovery issue, I flashed an older version of clockworkmod recovery and tried restoring after clearing my data, cache, factory reset, and Dalvik cache. Still, the exact same thing happened. I also tried restoring older backups, but the exact same thing happened.
What is going on, and what should I do? Thank you for your time.
Click to expand...
Click to collapse
its better to use titanium backup application for you.user friendly and worthy..
Hey guys, I've been silently stalking these forums for a while, but decided I wanted to be a part of this community myself. Anyway, here's my question:
I recently flashed CM10 onto my new Galaxy S3, and just decided that I like the functions of Touchwiz better than AOSP. No problem, I had made a backup, so I wiped my data and cache (not sure if that was necessary) and flashed back, then rebooted. Again, no issues.
However, I noticed upon flasing back that I had some blank home screens that I didn't used to have. Still no issue, I deleted them. However, my setting menu seems a little laggy when I press the options. As I said, this is a new phone for me so I'm not sure if it's my imagination, and I've never heard of issues with a restored backup happening before. On my old Droid 3, however, I think I noticed my gallery being slower when I flashed back to stock.
Anyway, any help would be greatly appreciated. Looking forward to participating here more.
Well, I have ran into that problem before with CWM. I'm not sure if the problem is or CWM. I much default to CWM as it very hard to screw up making CWM backup. I started using TWRP recently but I haven't used it yet to restore a back so I cant tell you if that one works better or just the same.
thetendy said:
Hey guys, I've been silently stalking these forums for a while, but decided I wanted to be a part of this community myself. Anyway, here's my question:
I recently flashed CM10 onto my new Galaxy S3, and just decided that I like the functions of Touchwiz better than AOSP. No problem, I had made a backup, so I wiped my data and cache (not sure if that was necessary) and flashed back, then rebooted. Again, no issues.
However, I noticed upon flasing back that I had some blank home screens that I didn't used to have. Still no issue, I deleted them. However, my setting menu seems a little laggy when I press the options. As I said, this is a new phone for me so I'm not sure if it's my imagination, and I've never heard of issues with a restored backup happening before. On my old Droid 3, however, I think I noticed my gallery being slower when I flashed back to stock.
Anyway, any help would be greatly appreciated. Looking forward to participating here more.
Click to expand...
Click to collapse
Do you backup with Rom Manager?
Gesendet von meinem GT-I5510
My bad, I ran ROM manager and flashed CWM Recovery 6.0.1.2.
When you use ADW launcher and do a backup with Rom manager, the phone doesn't shutdown clean, that resets the adw launcher.
(On my phone)
Gesendet von meinem GT-I5510
I'm not using a launcher, so it's not that. Should I move this to the Galaxy SIII forums? I figured it was just a general problem.
Did you by chance restore Titanium data/apps after you restored the Nandroid? I know one time I went from a Sense ROM to AOSP and restored my apps and app data from Titanium and my phone was going nuts. I reflashed my Nandroid and omitted the titanium restore and all was well.