I just tried a Nan restore. I had LauncherPro set as default before I ran the backup. After the restore my system booted into LP a lot was missing. I launched Sense and it also was messed up and gave the tip screen you get on initial out of the box startup.
I tried another backup with the same result. I finally used a third backup that was done before I installed LauncherPro and everthing was fine.
Can anyone explain this. Is there anyway to get my later backups back now?
marcmarshall said:
I just tried a Nan restore. I had LauncherPro set as default before I ran the backup. After the restore my system booted into LP a lot was missing. I launched Sense and it also was messed up and gave the tip screen you get on initial out of the box startup.
I tried another backup with the same result. I finally used a third backup that was done before I installed LauncherPro and everthing was fine.
Can anyone explain this. Is there anyway to get my later backups back now?
Click to expand...
Click to collapse
Can you elaborate on what rom, kernel, and what was missing?
Also you should be able to do a backup which will create backup with the current date and time. This is so you can later restore to that point to fix potential errors.
I backed up my stock rom with LP running as default over Sense.
I flashed to Virtuous 3.0.1 with adrynalyne kernel 2.6.32.15
I was missing my custom wallpaper and most home screen icons in LP. When I launched Sense same thing plus it acted like an initial out of the box install by showing me the pinch screen tip, etc.
I'm guessing but it seems that booting into LP on a sense rom caused the problem. As I said I went back to the previous backup, at which time I was also using LP and had the exact same result. When I went back to an even earlier backup, before installin LP, everything went fine.
I mentioned this on another post but then posted it as a new thread since it was off topic there and my post problem was resolved. I am told by another member that what I did is done commonly by others and the problem cannot be with the Nan backups. Can't think of another explanation though. Unlikely to get 2 corrupt nandroid backups, especially considering CW checks the md5.
When others restore to LP default has it been with Sense ROMs?
Just glad I had a lot of backups.
marcmarshall said:
I backed up my stock rom with LP running as default over Sense.
I flashed to Virtuous 3.0.1 with adrynalyne kernel 2.6.32.15
I was missing my custom wallpaper and most home screen icons in LP. When I launched Sense same thing plus it acted like an initial out of the box install by showing me the pinch screen tip, etc.
I'm guessing but it seems that booting into LP on a sense rom caused the problem. As I said I went back to the previous backup, at which time I was also using LP and had the exact same result. When I went back to an even earlier backup, before installin LP, everything went fine.
I mentioned this on another post but then posted it as a new thread since it was off topic there and my post problem was resolved. I am told by another member that what I did is done commonly by others and the problem cannot be with the Nan backups. Can't think of another explanation though. Unlikely to get 2 corrupt nandroid backups, especially considering CW checks the md5.
When others restore to LP default has it been with Sense ROMs?
Just glad I had a lot of backups.
Click to expand...
Click to collapse
Wow this sounds like dejavu lol exact same thing happened to me too with virtuous rom and launcher pro, I had 2 back-ups that were totally borked with the exact same problems you described, I thought it was only me seeing I was the only one that seemed to have this problem so I didn't report it. I saw my sd card was almost full and just assumed that was it.
Wow this sounds like dejavu
Click to expand...
Click to collapse
Well that's good to know. I'm still thinking it is flashing a Sense ROM and then not booting and loading Sense on initial startup. I don't know enough to know if this is reasonable, I'm just looking at the behavior. I can't think of another explanation.
I wonder if there is any way to get my later backups restored. Maybe something can be manually changed before boot up to put Sense back as default.
Related
Hi everyone, first post here. Looked around and haven't found an answer to this yet. Phone is EVO 4G
Have flashed this rom multiple times and the rom itself functions well with little to no lag. The problems arise if I do anything in recovery. Tried flashing a kernel (goldenmonkey) and wound up with endless force closes. Did a nandroid restore to a state just before I had flashed the kernel and the force closes continued. Shouldn't the restore have returned everything to the previous state with the stock kernel as that was what I had installed with the rom? That's what always happens with the other rom I have saved on my SD card.
Just a few minutes ago, I reflashed the kingedshooter rom, installed apps, etc. Was planning on trying another kernel, but forgot to put the zip on my SD card. Anyway, I did a nandroid backup (with everything working fine) and as soon as I rebooted the phone, I could not access the settings and the power control widget I had loaded on one of my home screens was gone. I couldn't make phone calls, and would get a force close if I tried to access any settings. Tried to restore to my most recent backup where once again everything was working perfectly and am still having the issues I just described. Anyone know what's going on? Thanks.
Anyone that reads this, please disregard the above. Made a nandroid after installing a theme and kept trying to go back to that. Thanks.
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.
So i was doing a little flash dancing between ROMS today, don't know if adding the new FP1 modems is what caused this or not, but restore wouldn't work. I tried restoring to tweakstock and got an md5 error, tried restoring to eclipse and infinity and both gave the same md5 error. I tried an old ass backup file from a few months ago, that one installed, but got stuck in a bootloop and couldnt get out of it no matter how many times i tried wiping data and restoring that backup. So basically i had to start from scratch, went with tweakstock and for some reason ive had a few issues. 1. google backup and restore wouldnt restore any of my apps which sucked, luckily i have titanium too. Contacts wouldnt sync to SNS facebook account, had to install the damn app to sync contacts. And lastly, the market is, well...still the market, and the froyo one at that. Usually it would upgrade itself when i first try to download something, but not this time. any ideas??
[Q] Restore didnt work and now stuck with old market
So i was doing a little flash dancing between ROMS today, don't know if adding the new FP1 modems is what caused this or not, but restore wouldn't work. I tried restoring to tweakstock and got an md5 error, tried restoring to eclipse and infinity and both gave the same md5 error. I tried an old ass backup file from a few months ago, that one installed, but got stuck in a bootloop and couldnt get out of it no matter how many times i tried wiping data and restoring that backup. So basically i had to start from scratch, went with tweakstock and for some reason ive had a few issues. 1. google backup and restore wouldnt restore any of my apps which sucked, luckily i have titanium too. Contacts wouldnt sync to SNS facebook account, had to install the damn app to sync contacts. And lastly, the market is, well...still the market, and the froyo one at that. Usually it would upgrade itself when i first try to download something, but not this time. any ideas??
Click to expand...
Click to collapse
I don't think it is the fp1 radio or more people would be dealing with the same issues especially flashing the full fp1 rom we've got. What kernel/rom were you using before you went all "flash happy" . I am thinking maybe you had ext4/lagfix enabled, and then you tried to restore a nandroid that was rfs enabled? Also when you say you started from scratch.. do you mean that you wiped and then flashed tweak through CWM, or that you odin'd back to stock with the pit file, which would likely fix your issues especially if they are partition related (might as well since you haven't been able to nandroid restore anyway).
ive been on pjb since january, all the restores were also pjb. the only difference has been the fpo1 modem. but ill prob odin back to stock n see if that does anything over the weekend...fingers crossed
Cool
cnoevl21 said:
ive been on pjb since january, all the restores were also pjb. the only difference has been the fpo1 modem. but ill prob odin back to stock n see if that does anything over the weekend...fingers crossed
Click to expand...
Click to collapse
Sounds good, lemme know if that fixes you up, it definitely should. One of the reasons I love my droid so much is that you can f**k it up in so many ways and 99% of the time you can get right back to stock and try again .
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.
Hey, I just installed my first ROM, and I cannot seem to get the dialer to work. Whenever I try to open it, it force closes, and "android.process.acore has stopped" keeps appearing. Any help? I wiped everything as shown in the thread, and I tried to restore my contacts using Titanium Backup, and I think that may have been the problem. No one else on the thread reports this problem, it seems. Everything else seems to work.
What Android version did you come from before HellKat? I think there's sometimes issues restoring things from previous versions of Android.
It may also be another app... I did a quick Google search and things like Facebook and Hotmail came up, removed and all was well again.
I came from stock 4.1.2 rooted, I'm guessing this means I can't restore JellyBean system data/apps, only from other KitKat ROMs?
nossmeet said:
I came from stock 4.1.2 rooted, I'm guessing this means I can't restore JellyBean system data/apps, only from other KitKat ROMs?
Click to expand...
Click to collapse
Before I continue, disclaimer, I'm not a dev or anything. I'm just trying to help with what I've picked up over my time here.
Hopefully you followed the nandroid step. Go back to your stock ROM and have Google backup your contacts. It's never let me down in restoring my contacts on a new ROM.
Sorry for the confusion, but yeah, it's a bad idea backing up system apps, especially with the changes to the dialer (among other things) in Kitkat. Games and other apps should be fine, though.
asimowalk said:
Before I continue, disclaimer, I'm not a dev or anything. I'm just trying to help with what I've picked up over my time here.
Hopefully you followed the nandroid step. Go back to your stock ROM and have Google backup your contacts. It's never let me down in restoring my contacts on a new ROM.
Sorry for the confusion, but yeah, it's a bad idea backing up system apps, especially with the changes to the dialer (among other things) in Kitkat. Games and other apps should be fine, though.
Click to expand...
Click to collapse
Yeah, I made a backup, so now I'm back to stock rooted. Thanks for the help, I'll keep that in mind when flashing back to HellKat.
What recovery are you using and what gapps package?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app