Problems with a new CM7 install - EVO 4G General

Hey guys. I've had it with MIUI. and i'm ready to switch to a new rom. i figured now was as good a time as any to try out CM7. So i downloaded the latest stable version, backed up my existing install and flashed. The phone got stuck at the bootscreen. I assumed it was because i neglected to wipe data and cache, so i went back, wiped everything, reflashed and booted into CM7(after an extensive wait)
Everything was running great and i just finished restoring my apps with MyBackup. I was getting FCs on a few apps, but i chocked it up to CM7 not having all the components that some of those apps require. I was about to start removing the offenders when the phone crashed and went back to the bootscreen. It sat there for 2 hours before i pulled the battery and restored back to MIUI.
In short, i really want to try out CM7, but if it's going to be this unstable, obviously it won't cut it. Am i doing something wrong??

Some apps just do not play nicely when being restored from a backup. Can you restore apps 1 at a time so that you only get the apps that you know work? Then re-download the apps that are causing problems.

Possibly. That seems like an unnecessary step though. Would a rom really crash because of app incompatibility? I thought they would just FC every time i tried to run them, not blow up the whole ROM.

If you are using ROM MANAGER you can try to use the utility for "Fix Permissions". I'm sure there is a way to do it in the recovery them selves, but the process escapes me.
This is not an uncommon requirement when restoring from one complex ROM to another.

I had some quirkiness restoring a few apps with Titanium backup. I ended up just reinstalling them from Market and haven't had issues since. Also, after restoring my contacts with Mobile Backup II, I could not edit them from the phone. Force closes. Had to delete them and re-sync with Gmail and exchange server. No problems after that.

I have flashed Synergy, Swagged Out Stock, SavagedZen, and a few others and always wandered back to CM7. In my experience, whenever you switch ROMs like that, there are always quirks, so I have taken to getting apps one at a time from MyBackup Root when I do switch. And yeah, I have had App conflicts cause forced bootloops before, it is not completely unheard of. I second the notion of installing one at a time, and Market DLing any that force loops. And as always, I reccomend a cache/dalvik/data whipe when switching full roms.

Related

The process com.android.phone has stopped unexpectedly

I have been having this issue ever since my phone booted up and all my apps sequentally had force close dialogs happen. I am running my apps from the SD and figured something went wrong with the boot up sequence. I tried doing a nandroid backup, reinstall fresh 1.1, but no luck.
I then used my backups to reinstall over all my apps, then went into Market to install them via that. Everything seemed to be just fine, but the phone app would still not dial anything and when I recieved a call, it gives the error "The process com.android.phone has stopped unexpectedly" and then proceeds to try to reset the phone connection. Most times I lose all data connection and need to reboot.
Recently, I tried installing the latest Modoco CDMA rom. No luck. I then did a Titanium backup and force reinstalled everything again. Still no luck.
Anyone have this issue and get it resolved? My Hero can do everything but make and accept calls. I really don't want to do a wipe as this problem can just happen again, so I would rather understand the process.
Thanks in advance.
Ceger
Simplest way to fix this should be clearing the dalvik/boot cache from fresh's kitchen. I really should write up a guide on how to do these simple tasks manually.
obelisk79 said:
Simplest way to fix this should be clearing the dalvik/boot cache from fresh's kitchen. I really should write up a guide on how to do these simple tasks manually.
Click to expand...
Click to collapse
Will that work on MCR 2.2 as well? I'll look into that. Is it something I can do from recovery?
Ceger
yes should work on mcr 2.2 and can be done manually from recovery, I know recovery does dalvik cache, not sure if it also kils the boot cache as well though. The older version only did dalvik.
obelisk79 said:
yes should work on mcr 2.2 and can be done manually from recovery, I know recovery does dalvik cache, not sure if it also kils the boot cache as well though. The older version only did dalvik.
Click to expand...
Click to collapse
Do you need to do both? Wiping the dalvik cache created lots of app fc issues, which would be fine if the phone actually worked. Still won't make or receieve calls.
And thank you for the assistance.
Ceger
Edit. Clearing the boot cashe got rid of the FC issues. However, still have same issue with the phone app. This is so annoying.
honestly the best bet to clear up the issues would be to do a full wipe from recovery. Wipe the phone clean then run the stock RUU and re-root and install your custom rom. Do a nandroid backup first just to prevent losing any of your info.
Unfortunately despite the many well written guides here on XDA there are always a few issues most likely a result of slight hardware quirks or unfortunate circumstances at the time of flashing.
Just for '****s and giggles' have you tried pulling your battery for 30 seconds, reinstalling it and booting the phone up?
Heck sometimes just a reflash of the rom right over top of itself. I've been tinkering with this phone since the day root came out and I still don't fully understand all of it's quirks.
Ceger said:
I have been having this issue ever since my phone booted up and all my apps sequentally had force close dialogs happen. I am running my apps from the SD and figured something went wrong with the boot up sequence. I tried doing a nandroid backup, reinstall fresh 1.1, but no luck.
I then used my backups to reinstall over all my apps, then went into Market to install them via that. Everything seemed to be just fine, but the phone app would still not dial anything and when I recieved a call, it gives the error "The process com.android.phone has stopped unexpectedly" and then proceeds to try to reset the phone connection. Most times I lose all data connection and need to reboot.
Recently, I tried installing the latest Modoco CDMA rom. No luck. I then did a Titanium backup and force reinstalled everything again. Still no luck.
Anyone have this issue and get it resolved? My Hero can do everything but make and accept calls. I really don't want to do a wipe as this problem can just happen again, so I would rather understand the process.
Thanks in advance.
Ceger
Click to expand...
Click to collapse
use these commands to clear cache
rm -r /data/boot-cache/
rm /data/dalvik-cache/
once you finish then reboot.everything should go away...
he's done that already.
then i suggest to extract the rom zip file, and get into command on your device and go under the system/lib or app and see what is listed in the folders. and compare it to the rom folder.
That's how i was able to fix the voice search on my device, one of the lib file was missing and got it to work after that.
obelisk79 said:
honestly the best bet to clear up the issues would be to do a full wipe from recovery. Wipe the phone clean then run the stock RUU and re-root and install your custom rom. Do a nandroid backup first just to prevent losing any of your info.
Unfortunately despite the many well written guides here on XDA there are always a few issues most likely a result of slight hardware quirks or unfortunate circumstances at the time of flashing.
Just for '****s and giggles' have you tried pulling your battery for 30 seconds, reinstalling it and booting the phone up?
Heck sometimes just a reflash of the rom right over top of itself. I've been tinkering with this phone since the day root came out and I still don't fully understand all of it's quirks.
Click to expand...
Click to collapse
Done and done and no difference.
reddick said:
then i suggest to extract the rom zip file, and get into command on your device and go under the system/lib or app and see what is listed in the folders. and compare it to the rom folder.
That's how i was able to fix the voice search on my device, one of the lib file was missing and got it to work after that.
Click to expand...
Click to collapse
Done, even manually moved some files in case they were corrupted at one point. Very bad move, nandroid backup was my friend there.
Guess a wipe will be the only option then. How annoying.
Thanks for all of your inputs.
Ceger
Another thought... would updating my phone with latest kernal compile possibly do the trick? Or how about a replacement process for google.com.phone?
Ceger
Interesting theory.... worth a try.
i had this issue once and it was because of somehow the uids for the apps got messed up. a wipe should fix this in most cases. but for me it went like ur issue. i almost event went back stock. then i looked into it and found that in my packages.xml file the the uids were all messed up. i had multiple uids and certs for the apps i was having issues with. so what i did was pulled the packages.xml from the device and erased the apps i was having issues with. then pushed it back and rebooted. that cleared the issue. so if i were u i would research that. do a google search on it. then if it doesnt work do the ruu and reroot. good luck man. i know how u must be feeling. i was there
toastcfh said:
i had this issue once and it was because of somehow the uids for the apps got messed up. a wipe should fix this in most cases. but for me it went like ur issue. i almost event went back stock. then i looked into it and found that in my packages.xml file the the uids were all messed up. i had multiple uids and certs for the apps i was having issues with. so what i did was pulled the packages.xml from the device and erased the apps i was having issues with. then pushed it back and rebooted. that cleared the issue. so if i were u i would research that. do a google search on it. then if it doesnt work do the ruu and reroot. good luck man. i know how u must be feeling. i was there
Click to expand...
Click to collapse
Actually, the fix was much simpler. I wiped the SD ext partition and just did a Recovery Wipe. It went back to stock modded rom that remained rooted. I then used Titanium to reinstall my apps with data and then MyBackup to get back some settings such as my scenes, etc. and all was good. Took all of 30 minutes to get my Hero back up and running in better condition than before.
Thanks all for the assists.
Ceger
com.android.phone
com.android.phone
i am facing this prob on cyanogen mod10....when ever i reboot my optimus 2x....i face this damn problem
help plzzzzzzzzzz.....!!!!!

Some super-simple noob backup questions

Quick and to the point:
1. Is a clockwork backup a full image of the system, such that if I restore from it no matter what kernel, rom, mod, etc. I've installed, I get exactly the completely system and state that I had when I made the backup? I.e., it is a true failsafe against messing up the phone, so long as CWR will boot and the SD card is intact?
2. A complete backup with Titanium, backing up all apps and system data, is a migration path for trying a new ROM? IOW, I can simply do a complete backup with Titanium, wipe wipe wipe, install the target ROM, then restore "missing apps and data" from Titanium and -- voila! I'm on the new ROM, but with all my apps, configuration, etc. I had before?
I'm getting ready to try out the Syndicate ROM...
dwallersv said:
Quick and to the point:
1. Is a clockwork backup a full image of the system, such that if I restore from it no matter what kernel, rom, mod, etc. I've installed, I get exactly the completely system and state that I had when I made the backup? I.e., it is a true failsafe against messing up the phone, so long as CWR will boot and the SD card is intact?
2. A complete backup with Titanium, backing up all apps and system data, is a migration path for trying a new ROM? IOW, I can simply do a complete backup with Titanium, wipe wipe wipe, install the target ROM, then restore "missing apps and data" from Titanium and -- voila! I'm on the new ROM, but with all my apps, configuration, etc. I had before?
I'm getting ready to try out the Syndicate ROM...
Click to expand...
Click to collapse
Ha! I am searching now for the exact same question! I am looking to try the Epic Experience. I will follow this thread to see what the answer is.
Thanks.
First off might I comment that Syndicate Rom is a great choice. Not just saying that cause any of them are my buddies either, cause IDK Any of them... so far though Running Syndicate Rom/Kernel with SetCPU at 200-1200 has been the smoothest Rom experience I have had up to date.
1. Is a clockwork backup a full image of the system, such that if I restore from it no matter what kernel, rom, mod, etc. I've installed, I get exactly the completely system and state that I had when I made the backup? I.e., it is a true failsafe against messing up the phone, so long as CWR will boot and the SD card is intact?
Click to expand...
Click to collapse
Yes in theory it is a backup of everything, data, apps installed, boot, system, literally the entire phone is backed up. Is it a failsafe though? I would rather say not. On some phones we can restore a clockwork recovery and have no issues, but since I've had my epic and switched around with different Roms, I've noticed that restore dosen't work quite as it should, probably because Roms are so much different, and you run into FC's, boot loops, and other issues... Restoring peices in advanced restore works well but a complete restore almost always has bugs.
True statement though that even if you screw up and get a boot loop, or constant force closes/phone restarts, as long as you can get back into clockwork your phone is not screwed. You were right on that one. So no worries if you wanna test and play.
2. A complete backup with Titanium, backing up all apps and system data, is a migration path for trying a new ROM? IOW, I can simply do a complete backup with Titanium, wipe wipe wipe, install the target ROM, then restore "missing apps and data" from Titanium and -- voila! I'm on the new ROM, but with all my apps, configuration, etc. I had before?
Click to expand...
Click to collapse
You have the idea right. You really don't even need to back all your apps up with titanium anymore these days, though, it too is plagued with FC's and problems. If you are using clockwork recovery, and you have made a backup already... all you have to do when installing a NEW rom is first wipe-fest, then let it boot once, then restart, go to clockwork, go to Advanced Restore, and ONLY restore the DATA part. (Reason for this is if you restore Boot, System, etc it will try to restore the Rom you just installed... Data is where all your apps/settings are at) This will do exactly the same thing as titanium backup will do, only with less bugs and alot easier.
Cool... thanks for the great response.
It's too bad there isn't an iron-clad, 100% reliable means to take a snapshot of the phone that can be restored reliably.
On WM it was simply a matter of using one of the various backup utilities (I used SPB Backup 2) to make an image of the system. No matter what I did to the phone, I could always wipe it back to factory clean, then restore from backup and have my phone back exactly as it was, with no issues.
I'm trying a CW backup, factory reset, restore cycle right now to see what happens. I'll report back on my experience.
EDIT: Okay, one deviation from the WM experience: The factory reset did NOT reset the kernel -- MixUp is still showing as the running kernel. Is Odin the only way to get the factory kernel back?​No matter what, I'm on my way after that to the Syndicate ROM!
EDIT: Okay, the CW restore seems to have restored everything back to the way it was, without problems after some brief playing around. No FCs (so far). On to wiping again, installing Syndicate Standard, then restoring data from CW as recommended here.​
OperationMove said:
You have the idea right. You really don't even need to back all your apps up with titanium anymore these days, though, it too is plagued with FC's and problems. If you are using clockwork recovery, and you have made a backup already... all you have to do when installing a NEW rom is first wipe-fest, then let it boot once, then restart, go to clockwork, go to Advanced Restore, and ONLY restore the DATA part. (Reason for this is if you restore Boot, System, etc it will try to restore the Rom you just installed... Data is where all your apps/settings are at) This will do exactly the same thing as titanium backup will do, only with less bugs and alot easier.
Click to expand...
Click to collapse
Alright I took the plunge and it seemed to work well. Some things that I noticed was that on first boot (before I did the restore), all of the preinstalled apps showed up (for instance, wireless tether, wired tether, launcher pro, etc...). Since I did a restore of the data, all of MY apps are there, but some of the apps that were preinstalled disappeared. Not all of them, though. For example, Launcher Pro and Wired and wireless tether disappeared, but Car Home is still there.
Another thing to note is that my widgets on the home screen don't seem to function correctly at first. I had to remove them and readd them to the home screen for them to work.
Other than that, everything is as it should be.
hotwired34 said:
Alright I took the plunge and it seemed to work well. Some things that I noticed was that on first boot (before I did the restore), all of the preinstalled apps showed up (for instance, wireless tether, wired tether, launcher pro, etc...). Since I did a restore of the data, all of MY apps are there, but some of the apps that were preinstalled disappeared. Not all of them, though. For example, Launcher Pro and Wired and wireless tether disappeared, but Car Home is still there.
Another thing to note is that my widgets on the home screen don't seem to function correctly at first. I had to remove them and readd them to the home screen for them to work.
Other than that, everything is as it should be.
Click to expand...
Click to collapse
Hmmm... okay. So just to provide a different datapoint, I'll go the Titanium route to get my own apps and settings back, and report. I'm guessing CW wiped the DATA partition before the restore, wiping out the pre-installed stuff from the ROM.
dwallersv said:
Hmmm... okay. So just to provide a different datapoint, I'll go the Titanium route to get my own apps and settings back, and report. I'm guessing CW wiped the DATA partition before the restore, wiping out the pre-installed stuff from the ROM.
Click to expand...
Click to collapse
Ok, since yesterday, I tried both ways. I did a wipe back to the default Syndicate Rom and installed Titanium Backup. While restoring, I noticed that not all apps would restore (seemed to be ones that were in the stock ROM so it's understandable). I did a restore of apps + data. Now, I had most of my apps back, however, I noticed that some of the data was missing. For me, most importantly was the SMS Messages. I also wanted to note that doing an application by application restore of the backup was very time consuming! I had to basically reinstall every app (and then Titanium restored the data)
Nandroid doesnt seem to touch the kernel on our phones ether I noticed. I had a problem yesterday after I flashed a new rom and when I went to do a restore through nandroid I got a bootloop. Once I reflashed the kernel it fixed the bootlooping problem. I have noticed this in other instances to with kernels not being backed up since I did one after I rooted my phone so I would have a stock image.
Thanks guys on your experience and feedback on the backup thing that I'm wondering what to do after stock root.
dito33
Sent from my SPH-D700 using XDA App
pyroswithoutfire said:
Nandroid doesnt seem to touch the kernel on our phones ether I noticed. I had a problem yesterday after I flashed a new rom and when I went to do a restore through nandroid I got a bootloop. Once I reflashed the kernel it fixed the bootlooping problem. I have noticed this in other instances to with kernels not being backed up since I did one after I rooted my phone so I would have a stock image.
Click to expand...
Click to collapse
This is what I have been told in the past- a nandroid restore does not replace the kernel

[Q] ACS force closing Logs Provider on boot

I'm running the latest version of ACS, and I keep getting a force close loop for "com.sec.android.provider.logsprovider", when I boot. Meaning I tap force close, and it comes right back, giving me no access to my phone. This is after two crashes (using the phone then it turns off). Does anyone have a suggestion? My father's Evo did this too, and he had to scream at Sprint before they'd swap the phone, but it's working fine now. I have the insurance thing on my plan, should I try that? If so, would I have to use Odin first?
Did you try to restore a backup with titanium backup??? I would boot to clockwork recovery and try to fix permissions by going to advanced in the menu.
Already done. I wiped user settings or whatever too. I'm now trying to reflash ACS and it says can't open /sdcard/foo/bar/syndicatefro110-standard-signed.zip (bad) could it be my sdcard? Does Sprint cover those under my hardware thing? I'm using ext4 afaik.
Im not sure if the cover the sd card I want to say no unless it is under a month old. However I wouldnt bring the phone in like that I would odin to a stock unrooted rom. Try to recopy the acs rom to the root of your sd card and then wipe data/factory reset 3 times in clockwork and then try to reinstall the rom.
I've been having issues on all my roms, so I'm thinking it could be my sd card. I'll bring it in as a last resort. Don't want to Odin if I can avoid it. Thanks for the help.
the logs provider has to do with mms and call logs and the sd card shouldn't affect it since it is a system app data/data/com.sec.android.provider.logsprovider. Did you try to clear the dalvik in advanced within clockwork???
That's crazy, I'm having the same exact problem. I was running the latest ACS fine for weeks and then I just rebooted it and BAM, 'Force closes' like crazy!
I reformatted, cleared all cache and factory reset to no avail. I still kept getting the same things pop up. I finally installed it through the zip file the 3rd time and somehow iit's working fine. I lost all my apps and evidently they didn't back up to my google account.
I'm too scared to reboot myphone now since that's what seems to trigger the problem.
Anybody know the source of the problem?
Curious if your getting any oneDram errors in dmesg? Seems like you guys are starting to have those odd errors were seeing in the Bonsai 4.1.0 beta.
Sent from Bonsai 7.0.3
I don't think i saw a oneDram error message, I remember seeing force closes for most of the services or processes that usually run in the background like phone and DRM service.
The persistent force close message that kept popping up was the logs.provider one.
This problem is currently happening to me now
I'm to lazy to fix it now though by the end of the week I'll do something
This happened to me while I had very bad/varying signal
(0-2 bars on a six bar scale)
And low battery
(40%ish)
I clicked on my email app and while it was loading I locked my phone and walked toward a window for better signal
When I looked back at my phone it rebooted by it self and everything is force closing like email and messaging.
Sent from my SPH-D700 using XDA Premium App
Yeah that's very similar to how out started with me too. Actually it might be exactly how it started.
Please let us know what you find out, because I've actually had this problem once before with an ACS rom.
I had my phone do this the other day with the logs provider. Reinstalled the rom (ACS Latest) and the issue went away...
Brother has been having the same issue for weeks on his epic too. He was running Bonsai 4.0.1 getting the same force closes, only his started first when he tried to open his mms app... He installed the latest ACS to see if it was Bonsai, about an hour later got the force closes again until he had an endless loop again.
We checked our memory blocks just for giggles and noticed he has 3 bad blocks while i have 11... cant be the issue...
He would get those force closes on EB13 and DK28 too.
We always do the 3x 3x 3x dance in clockwork before installing a rom too...
Dont know if this info helps or not. He thought about going stock and hitting up a Sprint store today and taking out an insurance claim....
Sorry I missed this thread.
Here's what I want you guys to do.
Back up your sdcard to your pc. ( just the files you wanna save.
Format your sd card with your phone
put the rom zip on your sdcard
Back up everything with your favorite back up program. titanium or mybackup root.
Reboot into cwm make sure it's 3.0.0.6
Wipe data, cache, dalvik 3x's ( don't cheat )
Flash your rom.
Boot your phone.
Restore your back up from your backup program. ( apps only no data )
Reboot into cwm again.
This time only wipe cache and dalvik 3x's ( no cheating )
Reboot and you should be good to go
Sent from my SPH-D700 using Tapatalk
^ This is a guaranteed solution to any unexpected FC problems.
k0nane said:
^ This is a guaranteed solution to any unexpected FC problems.
Click to expand...
Click to collapse
I wish it was, but it isn't a guaranteed solution. It might work 99% of the time.
Sent from Bonsai 7.0.3
Top Nurse said:
I wish it was, but it isn't a guaranteed solution. It might work 99% of the time.
Sent from Bonsai 7.0.3
Click to expand...
Click to collapse
I said for FCs, not bricks.
I'm having the exact same problem with the same ROM. The other day it froze after I took a picture and wouldn't respond. Had to do a battery pull after which I was stuck in an endless boot loop.
Tried just reflashing the ROM from SD and no dice, then cleared all caches 3 times and reflashed and I had a working phone again.
Then about 10 minutes ago I was using the phone and it shut down out of nowhere, after that booted back up with a tone of force closes and now the log provider force close won't go away. I'm just going to switch ROMs cause this is ridiculous.
No need to do that. The solution for freezing is excrutiatingly simple - and if it only freezes when you're in the camera, you need only format your SD card.
Do that, wipe data, and reflash, and everything will work 100% perfectly.
i had this issue more than once. and any kind of restoration of a backup made after the fc started resulted in continued fc's. i had to start fresh no backup and restore.
darksideauto said:
i had this issue more than once. and any kind of restoration of a backup made after the fc started resulted in continued fc's. i had to start fresh no backup and restore.
Click to expand...
Click to collapse
As expected - Nandroid bad data, and your bad data will remain. Use MyBackup Root for that.
Just take a Nandroid backup and restore it when you're running properly - or use the zip in the development section to turn journaling on. No problem.

[Q] Got another new Epic, let's talk backup & restore strategies

After going through refurbs from Sprint, I was finally able to get my hands on a brand new in box Epic! I've rooted and flashed 4 Epics in the last week, only to have to return them to stock because of issues.
What is the best way to restore my apps and app data from my previous device? I don't care much about system settings, preferences, etc. I've done a full restore through CWM on a reurb, but that resulted in a bunch of problems (whether it be due to a lack of journaling, general SD corruption, or bad backups). This was done on an Epic that received the EC05 OTA, then flashed to SRF1.1 with the TZ kernel.
I have concurrent backups in:
- CWM
- Titanium Backup Pro paid version
- MyBackup Root
My only real concern is the market apps, Amazon apps, and their saved data. It seems that Titanium Backup is best, but I'd rather not have to sit there and keep pressing "Install" for all my apk files. How do you guys do it?
I suppose it's temporary given the pending GB release, but I don't think I can stay on the stock rom for 2 weeks...
I use cwm too back up. But if u have problems when u back up. Your going to have them when you restore. And why wait you want the stock sprnt gb rom? Go ahead and root and forget the ota there will be aflasable zip on here in a timly maner once the ota begins.
It backed up fine in CWM but the restore seems to cause issues (eg LauncherPro Plus running low on memory). I'll try a different SD card.
My option for now is to either flash+restore my data or run stock EC05. I think I'll pass on the latter because it feels so limited in comparison to SRF.
Doing the initial charge so I'll wait to get some input
I hear you I'm on srf 1.1.1 and I could nver go back to stock rom. I tried the gingerbread leak. Wow rfs and tock rom. Felt sooo slow
How do you like 1.1.1 compared to 1.1? I think I read that 1.2 is due out soon as well?
Just restore an entire cwm backup on the new epic, wipe cache ad dalvik, the erase /data/lost+found/ and /data/tombstones
Sent from my SPH-D700 using XDA App
Titatanium is the way to go to avoid old corrupted or incompatible data from your old clockwork backup.
Only problem with titanium is that if u dont use launcher pro it doesnt save homescreen settings like widgets or apps placed on the homescreen.
I like titanium a lot cause i have it backup nightly so i always have a recent backup
I've just learned to give it up and not have any sort of attachment to my apps. I dont even bother restoring backups anymore. I reflash all the time and after I've messed with settings and wallpapers and such, it only takes about 15 minutes in the market and setup to get my must-have apps up and running. 90% of the apps I download I hardly ever use and can just take the 30 seconds to get them from the market again. The only exception I can think of would be game progress if you're into that, and TB should be sufficient with very few problems if its just the games. Otherwise, most app data is just logins and preferences. Since I started doing it this way, I've had WAY less problems flashing roms and such, because there are less possible conflicts.

[Q] Any way to restore My Apps in Market?

Nookcolor with MN 4.5.25, 1.1 overclocked kernel. I had the market problem, but 4.5.25 cleared it up. It worked fine for a week or so. Then yesterday all of "My apps" disappeared from market except the several I paid for. I did the 4.5.25 market fix several times and the rename Vending.apk fix a couple of times, no cigar (I'm aware of the risk of appearing insane, so I won't keep doing the same thing over and over, at least not too many times). On the desktop Android Market, my account, "My Orders" shows only these same paid apps and two free apps (with no rhyme or reason as to which two, except both have been uninstalled by me). If this isn't clear to you, I am talking about the list of the apps I have downloaded on market. All of my apps are working fine on the NC.
If I find the rest of my apps on Android Market on the desktop, all are marked "installed". But they simply will not appear, no matter what I do, on the NC or on the "My Orders" screen on the desktop.
Short of downloading each again (my time, ambition, patience, and data allowance are limited) how can I restore the apps to list on "My apps" on the NC and "My Orders" on the desktop?
I have a Titanium backup taken a few days before the failure. Is this information kept in some data area in the NC and sync'ed to market? Could I restore an app or that app's data and get my apps back in sync? I hesitate to restore everything, as I am beginning to believe that I am digging a hole.
Waiting patiently for some informative responses, DaveD
I haven't resolved this problem, and am still waiting for suggestions. In the meantime, an additional problem. Whenever I install a new app, downloaded in the standard manner from market, market will then appear briefly when I try to load it again, then disappear. I then have to restore the market.apk with Titanium, after which i will work again until the next time I install an app. I will now see in the my apps section the same several paid for apps plus any additional that I have installed since the problem first occurred.
Please help if you can. I would like to fix this. DaveD
I am trying to figure out the best way to backup my data and apps.
I am between using Titannium Backup or Backup Pro.
Any suggestions....?
Also,
Do you know what's the easiest way to reboot into recovery mode?
I'm running CM7 off SD card. Tried the Power and N button combination, with no luck also tried selecting reboot into recovery mode from CM7 desktop.
Which backup?
Since no one else is responding, I'll give you my recommendation based on limited experience. I like Titanium, and after installing it quickly paid for the Pro version, for the simple reason that it allows multiple backups, which I consider necessary in any backup program. I don't know about backup pro. But overall, among the two dozen or so apps I run, both free and paid, Titanium Pro appears to be the highest quality of them all.
Regarding rebooting into recovery mode, I don't know how else to reboot . See the next item in this thread for additional info on that.
Well, since no one is either interested enough or can help, I took the plunge and fixed it myself. If there is any interest, here is the only answer I could come up with.
First, I tried selectively restoring system apps with Titanium. I ended up restoring 20 or so. All that did was got me deeper into it. At the end I could no longer download apps--it would come up with the infamous "starting download" and that was the end of it.
So I decided to start from scratch, attempting to revert the Nook to it's original 1.1 out-of-the-box unregistered version. I followed the directions in the Nook Wiki (don't remember the two items and don't have time to go looking, as will be the case with a lot of the explanation below). I started with the ADB interface and entered the reboot failure 8 count from the desktop, upon which it rebooted, but did so into ClockWorkMod recovery, and recovered to the MN 4.5.25 system I was trying to get rid of. So, ignorant as I am about how all this works, I did the eight reboot failures manually, same thing, same thing. Now, I guess I could have gone in and uninstalled ClockWorkMod, but didn't think of that. So next time I tried it (third), I had recovery reset all data and cache. Then when I rebooted I was in NookColor stock 1.2, without rooting. But every time I tried to get back to out-of-the-box 1.1, I entered recovery again.
Now, withe the expectation that I could reinstall MN for the express purpose of killing ClockWorkMod recovery, then go about following the directions in Wiki which should work, I MN'ed it. Upon reemerging into MN, market worked! So I installed the 1.1Ghz kernel, and started reinstalling the apps, which I am still doing. No need to go back to the 1.1 clean level, as far as I have seen. Some of the old apps are still there, but most are gone. Again, no rhyme or reason as to which apps. But it works.
I could reinstall the old apps from Titanium, which I did for Dolphin merely to get the latest Beta 5.0.6 back and for the bookmarks, but for the most part am reinstalling from market, as I need for market to be aware of the apps I have.
Bottom line, it is much easier to wipe the Nook (provided you get ClockWorkMod out of the way first) and reinstall apps then to spend hours upon hours trying to figure out how to fix a market problem. Market is nice and solid with 4.5.25; I hope it stays that way this time (I don't know what caused the original failure, but I am highly suspicious that it was operator error)! I guess a clean wipe and reinstall to 4.5.25, including an overclocking kernel and apps, will take an hour or so, less if you reinstall apps from backups.
DaveD
titanium pro is the only way to go. buy it!. I had back up pro before and had to uninstall it because it would not reinstall from time to time. titanium pro always works and with the pay version you can batch activities not like the free version where you'll have to do it one by one. anyway, if you restoring with titanium pro remember to restore apps only and not the data. you don't want to pass on bad data to your fresh flash.
with the market did you try to clear cache in application manager? sometime this will help. go to settings / application / manage application / view all and scroll down to market and clear cache and data. I also think you'll need to clear cache and data with google services framework, but I forget, not sure.
for flashing nighties (only if you're going from cm to cm) all you have to do is wipe partition cache, not data and wipe dalvik cache and flash your new nightie. all of your app will be there. I hope this helped a little. good luck.
http://wiki.cyanogenmod.com/index.php?title=Barnes_&_Noble_Nook_Color:_Full_Update_Guide

Categories

Resources