I'm having trouble restoring a nandroid backup.
I had CM7 running nicely running from internal. But I got bored and wanted to try an ICS ROM. So, I booted into CWM recovery, and did a backup first thing. Then I did the whole wipe and flash thing, and got the new ROM up and running. After a couple days, I decided that ICS is still too flaky for everyday use, so I decided to flash back to my good ol' stable CM7. So I booted back into recovery, wiped, and restored the backup I had made previously. But when I boot up, things are wonky. I have my homescreen and wallpaper back, and many of my other customizations, but none of my apps seem to be installed. My homescreens have placeholder icons, and the widgets all have an error message.
I've tried restoring several times, with different combinations of wiping system, cache, dalvik, etc. But I've yet to hit the right sequence. What's the "correct" way to restore back to what I had? I hate to have to set everything up all over again.
What version of CWM are you using? Some of the older versions do not wipe the newer nooks properly.
If you really want to be sure you have wiped everything, go to my tips thread linked in my signature and get version 5.5.0.4 either for emmc or a bootable SD. Then flash my format partitions 5, 6, and 7 zip. Then restore your backup and see if that does it.
leapinlar said:
What version of CWM are you using? Some of the older versions do not wipe the newer nooks properly.
If you really want to be sure you have wiped everything, go to my tips thread linked in my signature and get version 5.5.0.4 either for emmc or a bootable SD. Then flash my format partitions 5, 6, and 7 zip. Then restore your backup and see if that does it.
Click to expand...
Click to collapse
I have version 2.5.0.1 now. Took a quick look at your tips thread - looks like I have some reading to do! I'll get a newer CWM and see how it goes. Thanks!
Sent from my NookColor using xda app-developers app
Related
Thankfully I have nandroids of Vaelpak and Myn2.2. I have tried synergy, stock rooted GB, and I can't remember the other two over the last couple days. Each time, it goes like this:
-Nandroid (typically from Rom manager out of laziness)
-Reboot into recovery
-wipe data/cache/dalvik (last few times I did this over and over)
-install zip of new rom
-boot loop
-pull battery and restore backup
I use CM 3.0.0.5 and have also tried RA 2.2.2.
I'm s-off (unrevoked forever).
My SD card is the last thing I can think of. I think I have to format and partition it (I know there are guides here...just never needed it). I just don't get it, I went through a phase where I was doing a new ROM every couple days and never had this issue. Thoughts?
Download Amon Ra 2.3, use as PC36ING.zip. Back up SD card to desktop. Format SD card, then partition it. Look in General or Development for a guide. Mount as MS (mass storage) and transfer files back, leaving out Android.secure, Android, RosieScroll, GoSMS and similar temporary folders and files. Nandroid, wipe system, data, dalvik, cache, factory reset, boot, android.secure and SDext twice. I would suggest VR Superwipe too. Flash new ROM and tweaks (if it is 2.3 Sense probably keep stock kernel). Reboot, enjoy new ROM.
Clockworkmod and AmonRa backups are not compatible.
Sent from my PC36100 using XDA Premium App
tropicalbrit said:
Download Amon Ra 2.3, use as PC36ING.zip. Back up SD card to desktop. Format SD card, then partition it. Look in General or Development for a guide. Mount as MS (mass storage) and transfer files back, leaving out Android.secure, Android, RosieScroll, GoSMS and similar temporary folders and files. Nandroid, wipe system, data, dalvik, cache, factory reset, boot, android.secure and SDext twice. I would suggest VR Superwipe too. Flash new ROM and tweaks (if it is 2.3 Sense probably keep stock kernel). Reboot, enjoy new ROM.
Clockworkmod and AmonRa backups are not compatible.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Other than getting amon 2.3 and copying the files back this was pretty much my plan. I was only going to restore my astro app backups after I get things running again. I do have VR superwipe...never worked with CM on the version I have.
Any reason other than preference for amon 2.3 (maybe the VR superwipe)? If I leave the SD blank but partitioned and just put the ROM back on it, is that an ok idea? I have it backed up...don't know if I have to have the file structure there.
also downgrading CWM down to 2.6.0.1 helped me flash the newer files and scripts as well if you dont like Amon 2.3. Just a thought!
As someone else suggested, you should either use a 'superwipe' script (flashable in recovery) or include /system in your wipe routine.
I don't get why people never wipe /system. That's where the entire ROM lives. If you don't wipe /system, then you are just flashing all kinds of ROMs on top of each other and you end up with a jungle of files from various ROMs all mixed together.
You might get lucky, many ROM devs account for this and wipe your /system partition for you before flashing the new files.
github said:
As someone else suggested, you should either use a 'superwipe' script (flashable in recovery) or include /system in your wipe routine.
I don't get why people never wipe /system. That's where the entire ROM lives. If you don't wipe /system, then you are just flashing all kinds of ROMs on top of each other and you end up with a jungle of files from various ROMs all mixed together.
You might get lucky, many ROM devs account for this and wipe your /system partition for you before flashing the new files.
Click to expand...
Click to collapse
Agreed. I don't believe in superwipes. But I DO agree to manually wile each category, except SD Card, including system.
What worked for me..
I had to upgrade my HBOOT from:
EVO_HBoot_0.76.2000
to
EVO_HBoot_0.97.0000
to load the Synergy ROM.
No wipe, wipe utilities, formats or partitions would work. Upgrading the HBoot fixed the boot loop issue... for me.
2k6_tx_dad said:
I had to upgrade my HBOOT from:
EVO_HBoot_0.76.2000
to
EVO_HBoot_0.97.0000
to load the Synergy ROM.
No wipe, wipe utilities, formats or partitions would work. Upgrading the HBoot fixed the boot loop issue... for me.
Click to expand...
Click to collapse
I am on the older HBOOT also. I will try this if the SD wipe and partition fails me. It could be this since it's recent ROMS giving me issue.
To the wipe /system comments...I did that one time for sure. Not each.
It's been a long while since I flashed a ROM and I am bit rusty on the process.
I downloaded the ROM for vision.
Where do I put it? On the phone or the external SD card?
Boot into CWM and then? Do I need to clear cache, data, anything?
And then I flash the ROM, right?
Put the ROM on the SD card. You can flash it from ROM Manager, or as you say boot into recovery and flash it from there. Make sure you backup your current ROM before you start though.
You should be fine just to wipe cache and flash it over the top.
Sent from my Desire Z running CM7.
Thank you. I tried doing that. A couple of issues:
1. Market showed only about 10 apps. I couldn't find all my apps. I thought market synced and downloaded any missing app.
2. More importantly, I could not download any app. I kept getting market error. I tried rebooting and wiping market data, but nothing.
I went back to the backup. Any pointers?
Back up your apps via titanium backup the do a full wipe the flash new rom, the restore apps via titaniumbackup
Sent from my T-Mobile G2 using xda premium
Any ideas on this one? I don't get any errors on the restore, but I am stuck on the eye every time I boot. I have tried wiping cache and dalvik cache.
About to just restore from Matt's tool, but this has me worried, you know?
Coronado is dead said:
Any ideas on this one? I don't get any errors on the restore, but I am stuck on the eye every time I boot. I have tried wiping cache and dalvik cache.
About to just restore from Matt's tool, but this has me worried, you know?
Click to expand...
Click to collapse
Well, have to say, thanks matt. The included RSD helped.
I forgot I was also restoring stock over CM10, which may have also been the issue, but I am back into the phone now.
You shouldn't have issues restoring backup from the older version, and you shouldn't have issues restoring a stock build over CM. Did you use the restore option or did you try to install the backup?
Sent from my Slim Scorpion-mini
RikRong said:
You shouldn't have issues restoring backup from the older version, and you shouldn't have issues restoring a stock build over CM. Did you use the restore option or did you try to install the backup?
Sent from my Slim Scorpion-mini
Click to expand...
Click to collapse
I have no idea what caused the issue. I did a backup of CM10, wiped data, cache, dalvik, and system. Hit restore on my old Stock backup (created in TWRP, not safestrap), wiped dalvik and cache again, and rebooted (and allowed TWRP to fix root first). It booted to the droid eye, but then just hung there for about 10 minutes.
I used Matt's utility to restore the system and it failed (tried to install the same part of system over and over again, 3mb in 4 seconds, 100k in .4 seconds, over and over again). So I had to force stop that and use RSD which worked fine.
No idea what all that was about.
So I think I found the culprit. My backups from the older version of TWRP don't have BOOT, only SYSTEM and DATA. So I was probably having my stock rom install while the CM10 BOOT was still in place.
The more you know
I'm having a little trouble understanding nandroid vs. other forms of backup and would appreciate some clarification. I'm running CM nightly on my Fido (Canada) G4. I took a nandroid as well as titanium backup of the factory stock image before I flashed CM.
A poster in the last thread I made suggested if I wanted to restore to stock, I could simply restore the nandroid, but I've also seen people say you shouldn't use nandroid to go across ROMs. My understanding is that nandroid is like having a filesystem backup, which would obviously not react well if you restored it over a new operating system (e.g. two different versions of windows). Or is nandroid more like say Acronis, which takes an entire disk image and overwrites everything?
Other misc questions:
- If I do restore via nandroid, do I need to wipe all data / cache / system data before or after the restore?
- I assume I can use titanium to restore SMS + all non-system apps across ROMs, which would save a lot of time.
- If I'm going from one CM nightly to another, would titanium work for system apps (e.g. all my settings, or contacts, etc)
- If I want to flash a new CM nightly, do I need to follow the entire wipe procedure just as if it were going from one ROM to a completely different one?
Thanks!
always make a nandroid in recovery. i recommend keeping it on your micro sd card. in the event you need to return your device to it's previously functioning state, restore the nandroid in recovery. if you are running an aosp rom and your nandroid is touchwiz, wipe data, cache & dalvik before restoring the nandroid. if the backup is on your micro sd then feel free to wipe system as well.
if you want to flash a nightly or update to a rom you are currently running, simply wipe cache and dalvik then flash the update, gapps and any custom kernel that you may be running.
i cannot answer your titanium backup questions because i do not use that program
xBeerdroiDx said:
always make a nandroid in recovery. i recommend keeping it on your micro sd card. in the event you need to return your device to it's previously functioning state, restore the nandroid in recovery. if you are running an aosp rom and your nandroid is touchwiz, wipe data, cache & dalvik before restoring the nandroid. if the backup is on your micro sd then feel free to wipe system as well.
if you want to flash a nightly or update to a rom you are currently running, simply wipe cache and dalvik then flash the update, gapps and any custom kernel that you may be running.
i cannot answer your titanium backup questions because i do not use that program
Click to expand...
Click to collapse
yes, that's about what I have. ok, thank you for the clarification of what to wipe! that's good to know.
re flashing a nightly/update: using your method should preserve system data yes? so no need to reinstall all apps or system data?
and thanks, I'll hold out hope that someone with titanium expertise will be able to answer that one
kabutar said:
re flashing a nightly/update: using your method should preserve system data yes? so no need to reinstall all apps or system data?
Click to expand...
Click to collapse
yes, system/user data will remain. understand, however, that if you perform one of these dirty flashes and you have a problem with the functionality of the ROM, you'll need to do a full wipe and flash to see if this clears the issue before you report the problem in the development thread.
kabutar said:
yes, that's about what I have. ok, thank you for the clarification of what to wipe! that's good to know.
re flashing a nightly/update: using your method should preserve system data yes? so no need to reinstall all apps or system data?
and thanks, I'll hold out hope that someone with titanium expertise will be able to answer that one
Click to expand...
Click to collapse
Your right on both titanium questions.. However its not recommended to restore system apps you backed up on a aokp/aosp ROM to a touchwiz ROM and the other way around... Other than that like I said your fine
Sent from my WANAM'ED AT&T S4
I was on Google edition using faux kernal. I decided to restore my stock rooted nandroid using twrp and I believe something went wrong. My phone rebooted on its own after the restore and everything went wrong from there. Force closes galore. I checked the kernal and it was still faux kernal so I figured that was the problem. I decided to wipe and restore one more time. This time it went smooth and I had the option to reboot when it was complete. Everything is running perfect but the weird thing is that the kernal appears to be stock now...
I'm very confused. Some Google searches led me to believe that a nandroid does not save your kernal but my kernal clearly changed on my second restore.
Does a nandroid restore kernal? What is the stock kernal for the i337 and is it around this site because I can't find it anywhere?
My kernal version reads...
3.4.0-453947
[email protected] #1
Sat April 27 17:06:05 kst 2013
Can someone confirm this is stock?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Cataligh said:
I was on Google edition using faux kernal. I decided to restore my stock rooted nandroid using twrp and I believe something went wrong. My phone rebooted on its own after the restore and everything went wrong from there. Force closes galore. I checked the kernal and it was still faux kernal so I figured that was the problem. I decided to wipe and restore one more time. This time it went smooth and I had the option to reboot when it was complete. Everything is running perfect but the weird thing is that the kernal appears to be stock now...
I'm very confused. Some Google searches led me to believe that a nandroid does not save your kernal but my kernal clearly changed on my second restore.
Does a nandroid restore kernal? What is the stock kernal for the i337 and is it around this site because I can't find it anywhere?
My kernal version reads...
3.4.0-453947
[email protected] #1
Sat April 27 17:06:05 kst 2013
Can someone confirm this is stock?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Yep, that's the stock kernel.
I'm not sure about TWRP. I know there are different options to save different partitions when creating a Nandroid with TWRP.
But there is something else I've been noticing through various posts about the S4. It seems that sometimes, with CWM, TWRP, or even ODIN, that some people have to flash files twice before they take. I'm not sure why it would be that way or if it's just a bunch of people screwing up on the first flash, but it sure seems that way. Maybe this is just one of those phones that depending on which lot you get, needs to be flashed twice?
yeah, Scott may be right. I don't think these recoveries are quite up to speed yet for the S4. Esp TWRP. I just like and have been use to TWRP UI.
Heard good things about Phil's Touch CWM--haven't tried yet. But, haven't restored yet either. Shabby's seems solid too. But, Phil's will restore both TWRP and CWM nandroids.
If you nandroided boot partition then the kernel should be restored
Only thing not touched in nandroids is radio
simply restoring the boot image from a nandroid will restore the kernel to what was backed up. I ALWAYS have a nandroid of a full factory ROM on my SD card in case I get problems. technically you don't even need to clear cache / dalvik cache.
note that some kernels actually flash more than the kernel and update Bluetooth and/or WiFi drivers, and would require more than the boot image to be restored.
keeping a fully stock ROM nandroid should be flashing 101... I've gotten into situations where I've had md5 mid matches when restoring backups, lost imei, all kinds of fun stuff. almost always doing a full factory reset/cache wipe/dalvik wipe/system format before restoring stock will fix those type of problems. after that I've had good luck then restoring the "problem" backup. very rarely have I ever had to Odin back to stock.
I installed a custom rom(GPE 5.0)on my i337m from Android 4.4.2 Stock ROM. I made a Nandroid backup with twrp 2830 before flashing the new rom. After playing with it a while I decided to go back to 4.4.2 using the Nandroid backup.
The Nandroid restore was successful(did a factory wipe before restore). However now I am getting force close non stop(seems like every app after the boot animation). I did a second restore without factory wipe and same problem. How can I get my backup restored properly?
If I install a custom rom(tried Goldfinger v9 among others), they boot fine. Any help would be greatly appreciated.
Thanks
TRoN_1 said:
I installed a custom rom(GPE 5.0)on my i337m from Android 4.4.2 Stock ROM. I made a Nandroid backup with twrp 2830 before flashing the new rom. After playing with it a while I decided to go back to 4.4.2 using the Nandroid backup.
The Nandroid restore was successful(did a factory wipe before restore). However now I am getting force close non stop(seems like every app after the boot animation). I did a second restore without factory wipe and same problem. How can I get my backup restored properly?
If I install a custom rom(tried Goldfinger v9 among others), they boot fine. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
Sounds like your nandroid is corrupted.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Sounds like your nandroid is corrupted.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I tried again, this time I did advanced wipe and selected the usual system, cache, dalvik etc...and also format internal sd. When I restored the nandroid backup it finally worked properly. Pretty sure the backup is not corrupted.