So, I took my phone into Sprint because all of a sudden I wasn't getting text messages, and my phone decided it always wanted to be on speaker.
They did their hard reset, and now I just want to know if it's alright to use my old nandroid backup, or should I install and change everything from scratch?
You should be fine. Just remember to wipe your data, system, cache, dalvik, and boot partitions with your recovery before restoring the nandroid.
Sent from my HERO200 using XDA App
Related
I am unable to use Google talk in cm9. It installs, but forces close when I open it...
factory reset and flash gapps again...it might help..
So, if I understand correctly....wipe cm9 to factory using webos. Then, reinstall cm9 and gapps?
Back up your apps using titanium backup or my backup pro. Go to recovery, take nandroid backup, factory reset, wipe cache, wipe dalvik cache, reflash cm9...reflash latest gapps....
Sent from my SGH-I897 using XDA
That did the trick!
Hi guys,
I believe this question has been asked multiple times, and i myself tried searching for answers from many various source to clarify my doubts, only to get more confused due to conflicting information.
Let's say now i am on a custom ROM. Before flashing the custom ROM, i made a backup of my stock touchwiz rom using cwm. However i want to revert back to the exact same state before flashing the custom ROM. What are the steps i need to do to restore the backup file?
1) Some sources mentioned just booting into cwm recovery, selecting "backup and restore" option, select "restore" and choosing the desired backup file will allow the phone to restore to the state prior to flashing.
2) Some other sources mentioned needing to wipe cache/wipe delvik cache/format system/format cache etc. first before i can restore the backup file.
So which is it?
Thank you!
Personally, I always choose option 2 if going to another rom. If restoring an earlier backup within the same rom i use option 1.
Don't know excact what the right thing to do is, but it never hurt to wipe cache / dalvik cache / system because you have it all backed up anyway. At least if you backup regulary. I back up regulary and delete the backups i don't want.
Cundis said:
Personally, I always choose option 2 if going to another rom. If restoring an earlier backup within the same rom i use option 1.
Don't know excact what the right thing to do is, but it never hurt to wipe cache / dalvik cache / system because you have it all backed up anyway. At least if you backup regulary. I back up regulary and delete the backups i don't want.
Click to expand...
Click to collapse
Thanks for the tip!
Is wiping cache/delvik cache sufficient in most cases?
Cos i saw a youtube video, where the guy did not wipe cache/delvik cache. instead, he formatted cache, data and system.
chainer22 said:
Thanks for the tip!
Is wiping cache/delvik cache sufficient in most cases?
Cos i saw a youtube video, where the guy did not wipe cache/delvik cache. instead, he formatted cache, data and system.
Click to expand...
Click to collapse
Wipe /
If problems format .
jje
Any other things i should look out for or preventive measures i should take for restoring backup from cwm?
i have been reading of cases where restoration through cwm fails and they have to go through the whole process of re-rooting and flashing before being able to restore it
there is no need for wiping, the recovery does it on its own prior to restoring.
got stuck
i erased everything followed 2nd step now its stuck on logo not starting
rishiud said:
i erased everything followed 2nd step now its stuck on logo not starting
Click to expand...
Click to collapse
Factory reset
factory reset
my phone is Zen Ultrafone 701HD there is no shortcut for recovery mode
rishiud said:
my phone is Zen Ultrafone 701HD there is no shortcut for recovery mode
Click to expand...
Click to collapse
Well you are in the wrong forum this is SGS3 I9305 .Not your phone ,
.......................................................................
My phone will currently not boot bast the CyanogenMod boot screen.
I flashed my phone several months ago to CM10.1 It was the update that patched the "masterkey" bug. I have been using it daily since then with no problems.
Today, I turn my phone on, and it just hangs at the boot animation.
There were no significant changes since the last time it was powered on. I think I installed McPixel from the humblebundle, and uninstalled a game from the playstore called Krog. No setting changes of any significance.
I've tried booting into safestrape and deleting both the cache and the dalvik cache, neither has helped. My stock rom still loads just fine, but i had factory reset it quite a while ago. I do have a backup of the rom from about 40 days ago i can try restoring, but i would love a more nondestructive way to fix this.
Try booting into safestrap, wiping system, cache, and dalvik, then reinstall the ROM and gapps.
Droid 4 - Avatar
kwyrt said:
Try booting into safestrap, wiping system, cache, and dalvik, then reinstall the ROM and gapps.
Droid 4 - Avatar
Click to expand...
Click to collapse
0.o wouldn't that be a LOT more destructive than just restoring the old backup?
pyro42 said:
0.o wouldn't that be a LOT more destructive than just restoring the old backup?
Click to expand...
Click to collapse
Nope. You are not wiping data so all your apps, setting, etc will still be there.
the data itself will remain if you just wipe the system, cache and dalvik cache but be sure to reinstall the latest stable build of CM and gapps for it
Sent from my XT894 using xda premium
kwyrt said:
Nope. You are not wiping data so all your apps, setting, etc will still be there.
Click to expand...
Click to collapse
ah gotcha gotcha...
unfortunately it didn't work.
for troubleshooting's sake, i went ahead and made a backup of the rom in it's non-working state.
i restored my old backup, it boots just fine.
restored borked backup (tested it, still won't boot), wiped cache/dcache, wiped system, installed cm-10.2-20130821-NIGHTLY-maserati.zip and gapps 20130812, wiped cache/dcache again for good measure, then reboot and waited 10 minutes, still won't pass boot logo.
so i figure someting's wrong with Data right? so i rebooted to safestrap and did a factory restore, then wiped cache/dcache, and still won't boot.
so now i'm going at it the opposite direction. restoring the working backup, restoring just the data from the nonworking backup, then upgrading CM/Gapps
rebooting.. and....
blank screen with full backlight. not so much as a CM logo.
i guess for now i am going to restore back to the old backup, update the rom, and go about reconfiguring, unless anyone has any more suggestions?
pyro42 said:
ah gotcha gotcha...
unfortunately it didn't work.
for troubleshooting's sake, i went ahead and made a backup of the rom in it's non-working state.
i restored my old backup, it boots just fine.
restored borked backup (tested it, still won't boot), wiped cache/dcache, wiped system, installed cm-10.2-20130821-NIGHTLY-maserati.zip and gapps 20130812, wiped cache/dcache again for good measure, then reboot and waited 10 minutes, still won't pass boot logo.
so i figure someting's wrong with Data right? so i rebooted to safestrap and did a factory restore, then wiped cache/dcache, and still won't boot.
so now i'm going at it the opposite direction. restoring the working backup, restoring just the data from the nonworking backup, then upgrading CM/Gapps
rebooting.. and....
blank screen with full backlight. not so much as a CM logo.
i guess for now i am going to restore back to the old backup, update the rom, and go about reconfiguring, unless anyone has any more suggestions?
Click to expand...
Click to collapse
Yeah, definitely sounds like something in /Data. Only other possible option I can think of would be to use Titanium Backup. It has an option to "Extract from Nandroid backup". It's under the "SPECIAL BACKUP/RESTORE" options. I've never used that option before so I have no idea how or if it would work but might be worth a shot.
kwyrt said:
Yeah, definitely sounds like something in /Data. Only other possible option I can think of would be to use Titanium Backup. It has an option to "Extract from Nandroid backup". It's under the "SPECIAL BACKUP/RESTORE" options. I've never used that option before so I have no idea how or if it would work but might be worth a shot.
Click to expand...
Click to collapse
wonderful idea, unfortunately TB crashes when i point it at either backup.
buuut i did find Nandroid Manager * ROOT which looks like it might be working.
if you really wanna see if it is the data or not have you tried to
flash 10.2 or whatever you started out with... then restore -just-
the data to the freshly flash system and then do a wipe of all
said caches... I do that sometimes to get a fresh start on my
os itself.. works pretty well. Just do not restore the cache just
the data part. Or restore with MD5 checking... if it doesn't check
out then you know for a fact that the data partition in that specific
nandroid isn't any good :/
Hi,
somehow the software of my galaxy note got damaged. I didnt install new firmware or anything. i just wanted to shut it down but i think it freezes already there. so i took the battery out. but when i start it it gets to the samsung boot anmation and crashes and restarts again.
i can reach the phils kernal and also bootloader. i hope i can do a custom flash to fix it without that i have to wipe it and reinstall anything. which part i have to reflash to fix that?
if you can reach the recovery, then make nandroid backup and wipe data and cache and dalvik and finally restore your cache and data (or you can reflash using odin and then restore data and cache).
Sent from my GT-N7000 using xda premium
Thanks! Tried it but I think the backup wasn't created correct. I couldn't restore data and cache.
well I used a some months old backup. had to update a lot and to do changes but it works now.
so I will create an actual backup now.
Stevie
Hi,
using CWM recovery, I restored a backup. Everything seemed ok, but the phone didn't go past the cyanogenmod logo.
I tried wiping cache, dalvik, and re-restored. Still nothing.
The only way I've found is to wipe the data; this way the phone started, but obviously it's like a brand new cyanogen install (it's not a restore...)
What went wrong?
Anything I can do???
I want to know why restoring the backup didn't work; I didn't get any error messages during backup or restore.
How can I trust the backups???