Related
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 recently bought an HTC One S. I came from an HTC Amaze 4G, and thus I backed up everything in Titanium Backup *AND* SMS Backup and Restore.
Thank goodness I backed up my texts in SMS B&R.
When I unlocked the bootloader and rooted the device, I went to install TB and restore missing apps and all system data.
I have never had this happen before, but when I rebooted the phone afterwards it said "Loading" on the HTC Sense screen and stayed there forever. It asked a few questions like Facebook login, etc. but still remained stuck on "Loading."
I eventually gave up and decided to take matters in my own hands. I figured that it's likely HTC Sense 3.6 data files were not compatible with 4.0 to a degree to cause issues, so I went into settings and cleared out the data for HTC Sense, and rebooted the phone.
When I rebooted the phone I was finally able to go into the messages app. Turns out I had a new text. NONE of my text message threads were there!!!
I am restoring them right now with SMS B&R.
I don't think this can be an ICS thing because on the Amaze I restored a TB backup the same exact way to a new ICS ROM and everything was fine. Has to be HTC Sense.
Anyhow, I just wanted to warn you guys. Don't trust a TB backup by itself from another device to the HTC One S. It may not work.
I see no reason to believe it won't work if coming from another phone with Sense 4.0, however I would be cautious and AT LEAST backup your text messages with SMS Backup and Restore.
It's still in the process of restoring. I am thinking that should surely work, but until it's done we won't know for certain. Will be certain to update this thread.
PS: I know some of you believe that you should never restore system data when going to a new device/rom (even though this is my 2nd post I've been lurking for quite a while :-D (as a guest)). I prefer to have all my stuff restored. If it causes a problem I am willing to go back and re-flash the rom
--
AR @}-,-`--
you cant restore system data from one phone to another, Thats a recipe for disaster. Even restoring from one ROM to another is risky...
Only ever restore apps and app data, Not anything else.. Ive been using TB for about 2 years now.. Never had a single issue with it
alexanderose said:
PS: I know some of you believe that you should never restore system data when going to a new device/rom (even though this is my 2nd post I've been lurking for quite a while :-D (as a guest)). I prefer to have all my stuff restored. If it causes a problem I am willing to go back and re-flash the rom
Click to expand...
Click to collapse
@ azzledazzle, did u see this? )
yes i saw it, but i dont get why you like to restore system data...
there is nothing of use in it if you are restoring using the same ROM, the data will be in that ROM anyway.
If you are restoring on a new ROM, you cant restore the old data lol
you like to restore system data, yet if you have troubles you wipe and skip restoring data..
Why not just skip system data altogether ?
You sound like you have OCD or something
azzledazzle said:
yes i saw it, but i dont get why you like to restore system data...
there is nothing of use in it if you are restoring using the same ROM, the data will be in that ROM anyway.
If you are restoring on a new ROM, you cant restore the old data lol
you like to restore system data, yet if you have troubles you wipe and skip restoring data..
Why not just skip system data altogether ?
You sound like you have OCD or something
Click to expand...
Click to collapse
System data saves the wallpaper, all icons, folders, etc. in the native launcher, alarms, etc. etc. which is not restored with apps. System data also saves the text messages, and restores them WAY faster than SMS Backup & Restore.
I've never had a problem restoring them until now. I tried one time not restoring system data, following the advice of someone on here who said it was pointless, and ended up losing system stuff. After that, never again do I restore without restoring system data.
Just curious if anyone else has experienced any of the following:
I was running CM10.0.0, but had that issue where my NFC was unchecked. So i wanted to restore to a TW ROM so i can check on NFC, restore back to CM10, etc.
I did a backup. Tried to restore my old TW (synergy r73), but got an error in CWM 6.0.1.2:
Error while Restoring /System!
Then i got the same message for ALL of my nandroid backups, including the newest one i made of CM10. I did some searching and found tons of folks with the same issues, but no solutions beyond.. format your SDCard properly (which mine is).
That's fail #1.
After being unable to restore, i just flashed CM10 zip again and started over. I did however use that new Titanium feature where it makes a flashable zip of all of your apps a few days back.
But every time i try to flash the zip, the phone resets in the middle of the install. I've never seem CMW crash and reboot.
That's fail #2.
I ended up restoring apps the old fashioned way, but regardless... any ideas?
Thanks,
Mangler