[Q] Why do my apps disappear after each restart? [2.3.4] - Captivate Q&A, Help & Troubleshooting

I have a major problem. When I restore apps using titanium backup, and then restart my phone, all of my apps disappear. They aren't restored to my SD card or anything, they just disappear. I'm not sure if this is a rom/kernel issue or a titanium backup issue. They show up in my Settings>Applications>Manage Applications but they show up as "com.xxxxxxx.xxx" and they don't appear in my appdrawer. I've been having this problem on Mosaic, Apex, and Obsession. The kernels I've tried are Talon and Existz Voodoo. Sorry if this question has been asked/solved but any help would be greatly appreciated. Thank you

It sounds like you are flashing cwm3 roms with cwm2. Try flashing a rom, then as soon as its booted, go into recovery and flash it again.
Or
Follow directions for installing a rom from the op of the rom thread. Follow them word for word.

Thank you so much. re flashing worked perfectly.
Sent from my GT-I9000 using XDA Premium App

Related

[Q] Does ROM Manager back up the ENTIRE phone?

Silly noob-like question, but I wanted to make sure before I continued messing with my phone.
Does ROM Manager back up EVERYTHING on the phone? For example, I backup my rom. Move the backup file onto my pc. Then I screw around with roms, lag fixes, etc. and totally screw it up. If I "restore" the backup made by ROM Manager, will all my apps, settings, desktop, data files, etc be exactly as they were before I started screwing around?
Or, would I need to use Odin to load the same ROM as that which was backed up and then run Rom Manager Restore?
Thanks!
Yes it does
Sent from my SAMSUNG-SGH-I897 using XDA App
Here's another question regarding this thread:
I have the lagfix mod which uses the internal sdcard. When I create a backup will it and restore exactly how it was including the lagfix partition? If yes, is it the same procedures or do I have to do it a different way with the extra partition?
Thanks in advance.
Deca4 said:
Here's another question regarding this thread:
I have the lagfix mod which uses the internal sdcard. When I create a backup will it and restore exactly how it was including the lagfix partition? If yes, is it the same procedures or do I have to do it a different way with the extra partition?
Thanks in advance.
Click to expand...
Click to collapse
Actually I am trying to figure out the same thing. I made a backup before I started messing around with lag fixes, different roms and so forth. Then the other day I tried to restore a rom it didn't work. Eventually I soft bricked the phone and had to make the USB Jig to get it working again. Needless to say I am very intrigued with what exactly Rom Manager does backup and its limitations but I can't seem to find it anywhere. I am thinking the reason my backup was screwed up was because of a lag fix, only problem is I can't remember what lag fix I had on it when I did the initial recovery.
Something from my experience to add here:
Scenario 1:
-----------
I backed up the original 2.1 JH7 on my phone.
Installed 2.2 custom ROM, and played around with it.
Backed up 2.2 ROM.
Messed up with my 2.2 custom ROM.
Went to ROM manager recovery, and recovered the backed up 2.1 JH7, and ended up messing up. My phone didn't even boot up.
Then I went back to recovery, and tried restoring the backed up version of 2.2.
Phone booted up into 2.2, but, started giving a lot of FCs.
Scenario 2:
-----------
Installed 2.2 custom ROM 1.
Backed it up.
Messed it.
Restored it - worked fine.
Installed 2.2 custom ROM 2.
Backed it up.
Restored the 2.2 custom ROM 1.
Everything working fine.
Looks like as long as the core OS is of the same version, it seems to work.
Maybe there is something in the boot sequence that's probably not being restored (???)
---------------
Edit: I do not have CWM app installed. I use the CWM update.zip recovery manager since its the least intrusive way.
diablo009 said:
Something from my experience to add here:
Scenario 1:
-----------
I backed up the original 2.1 JH7 on my phone.
Installed 2.2 custom ROM, and played around with it.
Backed up 2.2 ROM.
Messed up with my 2.2 custom ROM.
Went to ROM manager recovery, and recovered the backed up 2.1 JH7, and ended up messing up. My phone didn't even boot up.
Then I went back to recovery, and tried restoring the backed up version of 2.2.
Phone booted up into 2.2, but, started giving a lot of FCs.
Scenario 2:
-----------
Installed 2.2 custom ROM 1.
Backed it up.
Messed it.
Restored it - worked fine.
Installed 2.2 custom ROM 2.
Backed it up.
Restored the 2.2 custom ROM 1.
Everything working fine.
Looks like as long as the core OS is of the same version, it seems to work.
Maybe there is something in the boot sequence that's probably not being restored (???)
---------------
Edit: I do not have CWM app installed. I use the CWM update.zip recovery manager since its the least intrusive way.
Click to expand...
Click to collapse
Interesting, it would makes sense in what you are saying. My error that I go was when I went from my original JH7 backup, installed a rom based on JH6 and then tried to install my original backup. I might have to try JH6 roms and see if I can restore to them easily or not. I will have to wait for Micro USB cables to come in as I don't have a spare since I used my only cable to make the JIG.
The kernel and modem aren't backed up, so if your backups use different ones and you try to restore them you'll have issues.
I herd a rumor that rom manager doesn't work with froyo on the captivate. But I could be totally wrong.
Sent from my SAMSUNG-SGH-I897 using XDA App
peachpuff said:
The kernel and modem aren't backed up, so if your backups use different ones and you try to restore them you'll have issues.
Click to expand...
Click to collapse
This is what I have read about it as well
Voodoo
There is also a different version of CWM Recovery (what Rom Manager uses to back things up) for the voodoo lag fix.
tnerb123 said:
I herd a rumor that rom manager doesn't work with froyo on the captivate. But I could be totally wrong.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It works. I backed up and restored a few variants of Froyo ROMs.
peachpuff said:
The kernel and modem aren't backed up, so if your backups use different ones and you try to restore them you'll have issues.
Click to expand...
Click to collapse
How do I backup these? Is there any way?
If Ron Manager does backup the kernel and modem why would so many people have problems restoring back to different Roms? This is why I am so puzzled with this software.
Sent from my SAMSUNG-SGH-I897 using XDA App
Rom Manager can backup EFS folder ??
i lost my imei and the only backup that i have its from Ron Manager
Absolutely it does there!
Maybe I'm old fashioned, but best bet is backup from recovery. Saves everything down to browser login data. Can't go wrong with a full backup! I make one every time I flash just about anything.
Sent from my SGH-I897 using xda app-developers app
Rom Manager vs CWM Recovery
yes Rom Manager can do backup of phone..but why not just do
a Nandroid Backup from CWM Recovery..
never had problem with Nandroid Backup from CWM Recovery :victory:
dobi3 said:
yes Rom Manager can do backup of phone..but why not just do
a Nandroid Backup from CWM Recovery..
never had problem with Nandroid Backup from CWM Recovery :victory:
Click to expand...
Click to collapse
Agreed!
Sent from my SGH-I897 using xda app-developers app

android.process.media FC

I keep getting this error while trying to download anything from the Market.
"The process android.process.media has stopped unexpectedly. Please try again."
I'm running JH7 with SRE2b6 and this morning flashed the evo blackbar minimalistic v1.2 theme. I'm assuming the minimalistic theme is the culprit for this, although before JH7 I didn't have this problem while using it, though I themed that through Metamorph and this through stock recovery. Any ideas on how I can this fixed? Thanks!
I should also make note that I'm not able to access any of my images via the Gallery anymore... I tried flashing a different Minimalistic mod, tried using ROM Manager to fix permissions, all to no avail. Haven't seen anything else posted on here that I could try, hesitant to reload my Nandroid that is a couple days old :/
I've had this same error many times. Everytime I had to nandroid back to a backup weeks old as it only happened like every other month. For future reference all you need to do is nandroid backup complete wipe and restore.
I tried everything else and nothing worked including installing the rom on top of her over again, reinstalling the kernel etc. The only thing that worked for me was the above.
Clear app data?
Sent from my SAMSUNG-SGH-I897 using XDA App

[Q] Cog 2.1.1 eclair to Cog 2.4 froyo

I've been waiting to make the jump to froyo and with the new release of Cog 2.4, I figured I would do it now.
I've attempted to go through the 761 pages of the topic, but I just wanted to confirm the steps I'm suppose to take. According to the Cog wiki, I should just use rom manager to flash the new rom. This seems too easy. Am I missing anything?
Here are the steps I think I should take:
titanium backup apps and data
disable voodoo by putting folder "disable-lagfix" in /sdcard/Voodoo
nanodroid my current rom
flash cog 2.4 through rom manager
enable voodoo by removing folder "disable-lagfix" in /sdcard/Voodoo
restore apps and data with titanium backup
win
Am I forgetting something?
Some would tell you to wipe data and cache before installing new rom. Can't hurt.
I usually master clear, flash stock, root, install cwm, flash new Cognition, install Titanium Backup, reinstall apps. No troubles doing it this way, so far.
Sent from my SAMSUNG-SGH-I897 using XDA App
bah, I was hoping that I wouldn't have to master clear. I'll give it a try. Thanks.
b0bfath3r said:
bah, I was hoping that I wouldn't have to master clear. I'll give it a try. Thanks.
Click to expand...
Click to collapse
You might be able to flash without master clear. I just like to clean out as much of the old rom before I flash a new rom. YMMV
Alright, I was able to get it installed. No problems so far. Thanks for the help cappysw10
Well problem 1 my notification bar doesn't work. It just wont pull down
Sent from my SAMSUNG-SGH-I897 using XDA App
It happens at times, especially when doing cpu intensive tasks, reboot and it will work
swyped from a captivate running doc's jpo+setiron kernel
I should have thought of that. Thanks
Sent from my SAMSUNG-SGH-I897 using XDA App

Major miui 1.6.17 problems! Please help!

I installed MIUI 1.6.17 on my captivate yesterday and I've been having serious problems with it. I can't receive phone calls, the home button doesn't work, there is no lock screen, and I can't boot into any other rom or restore any of my backups. I tried master resetting the phone, but it did nothing. When I rebooted all my apps, settings, etc were still there as if I never reset it. I tried reflashing the rom but nothing has worked and I keep rebooting to the same problem filled phone. The same goes for flashing other roms. I tried flashing a different rom with no luck. Any help would be greatly appreciated!
Can you get into DL mode? If so use this to go back to stock eclair.
http://forum.xda-developers.com/showthread.php?t=731989
Sent from my SAMSUNG-SGH-I897 using XDA App
Please use the proper sticky for ROM-specific questions.
As miami said, please use the sticky. On that note, thread closed.

[resolved] S Memo does not work anymore

All of a sudden S Memo has stopped working. I have already tried a few things like deleting app data and cache, uninstalling the app and restoring a backup, making S Memo a user app... So far nothing has helped. I know I could reflash the rom but since I use the app very seldomly reflashing the rom seems to me like shooting with canons at birds. Any ideas? By the way, S Note and editing screenshots taken by the S Pen method works just fine.
My rom is LRQ and the kernel is PhilZ 2.5. Rooted, busybox installed, CWM too. Could it be the kernel? No it is not the kernel, I just tried cf-root to no avail.
Sent from my Galaxy Note running ICS
altae said:
All of a sudden S Memo has stopped working. I have already tried a few things like deleting app data and cache, uninstalling the app and restoring a backup, making S Memo a user app... So far nothing has helped. I know I could reflash the rom but since I use the app very seldomly reflashing the rom seems to me like shooting with canons at birds. Any ideas? By the way, S Note and editing screenshots taken by the S Pen method works just fine.
My rom is LRQ and the kernel is PhilZ 2.5. Rooted, busybox installed, CWM too. Could it be the kernel? No it is not the kernel, I just tried cf-root to no avail.
Sent from my Galaxy Note running ICS
Click to expand...
Click to collapse
Hi there, if you uninstall the app then restore the backup, you are essentially just replacing the same app? If there was an issue with the app then its possible that there is an issue with the backup? It may be an idea to fully uninstall the app, but rather than restore it, get an apk (its easy to find) and install the apk using a File Manager. If the system persists then it could be a problem with the Samsung Apps. If this is the case, then a reflash may be the best option.
I hope this helps. Please hit Thanks if it did.
I gave up and just reflashed the rom. There was also another issue and I came to the decision that it would be the best to simply reflash the rom. Seems like Linux based os are no better than Windows when it comes to suddenly appearing issues that can only be solved by reinstalling the os
Sent from my Galaxy Note running ICS
altae said:
I gave up and just reflashed the rom. There was also another issue and I came to the decision that it would be the best to simply reflash the rom. Seems like Linux based os are no better than Windows when it comes to suddenly appearing issues that can only be solved by reinstalling the os
Sent from my Galaxy Note running ICS
Click to expand...
Click to collapse
yeah I wouldn't disagree with that. After flashing a new ROM, I tend to Fix Permissions in Advanced Recovery, it seems to resolve any potential FC issues before they occur. Glad it's sorted though.

Categories

Resources