Database Users

[Q] NANDroid Experts...

Well, I get to join the ranks of the stupid. Ah well.
The objective: To "Re-build" a nandroid backup.
The cause: I wanted to use the new Netflix app, so I nandroided my Evil D 0.32 DHD ROM, downloaded Virtuous Fusion, went into recovery, and like the instructions said, wiped everything. In my tired state, I even did the SD card. Once done, I began to try to flash the new ROM, but could not find the zip. Cursing like a drunken sailor for forgetting to copy the zip file, I mounted the SD Card and my horror grew as I saw it was blank. Wiped.
Since then: I swapped my card with a spare, flashed a ROM, and began a recovery on the card. I got all 5 nandroids from the card back (at least I think I did)... but...
The issue: Each of the folder I recovered has 6 files inside: .android_secure, boot, cache, data, nandroid, recovery, and system. I rebooted into recovery, and tryto flash one. OFC, since they are no longer zips, it failed.
So I zipped one, and it fails as well. No error message just:
CWM Recovery .0.2.4
--Installing /sdcard/Nand1.zip
Finding Update Package
Opening update package
Installing Update
Installation aborted.
Root with gfree and eng hboot.
Ideas?

Just a quick bump and a status update...
Not sure why I was trying to flash backup when I needed to restore...
Anyways, I used the correct menu, restored a backup...
Good news is that 2 of the 5 backups restored no issue. Of the 3 dead ones, 1 was a stock backup, so I don't care about it. However, one of the other 2 is what I needed. (Meaning, the 2 that restored were old, and of the three ones that would not for MD5 issues, one I needed.)
So the question changes.
The 5 nandroids: 1 was stock, 4 were the same ROM, just taken at different points in time.
The reason 2 of them won't restore is failed MD5, which just means 1 byte (or more) has changed.
From what I know, the 6 files - .android_secure, boot, cache, data, nandroid, recovery, and system - all point to certain parts of the phone.
.android_secure - has to do with market from what I know.
cache - won't kill the phone if this is corrupt, cache will just rebuild.
data - the all important file. Your personal data is stored here. Apps, settings, etc.
nandroid - related to md5 and such? Not needed for apps/data
recovery - recovery image
system - the rom itself.
Now, if I am correct, if I restore a working nandroid, and then just the data from a dead nandroid, as long as the ROM was the same between the 2 of them, I should be golden?
right? And issues with this?

What are you worried about losing? Between Google sync and HTC sense sync you'll get most of the important stuff back.
Sent from my HTC Vision using XDA App

There are many apps which I no longer have a apk for that version (Soundhound? New version has permissions I don't want to give!) that I had there. And my TB backup was on the card as well...

So, anyone know if/how? In short: If I have a damaged nandroid and working nandroid of the same ROM, can I restore the data from the bad one to the good and how?

MordyT said:
So, anyone know if/how? In short: If I have a damaged nandroid and working nandroid of the same ROM, can I restore the data from the bad one to the good and how?
Click to expand...
Click to collapse
If you run an md5 of the data img you want, place that in the md5 file (included in the backup folder) it should restore properly. I've been in the same situation as you and that's what I did to fix it.
Sent from my HTC Glacier using XDA Premium App

[Q] Why does my evo hate new ROMs now?

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.

Nand Android not booting thru cwm Recovery

Hey,
I tried installing Android using cwm rec., everything goes well, but the android does not boot, it gets stuck on the booting screen, i tried several time, diff roms, still no results, can any one help me if im missing something? :S

make sure you are removing any leftover stuff from a previous rom on the SD card.
So in CWM, before you go to flash the rom, do a 'wipe data/factory reset' which should clear out the ext partition and the .androidsecure (or whatever its called) folder on the FAT32 partition.

I have done that, but it wont work, i've cleared cache too,
Btw how much time does it take on the first boot?

dont know, sorry, i've never used a sense rom, but i've seen posts referring to a good ten minutes or more, depending on the sd card and teh rom being installed, and how much stuff is moved to sd. Some roms just put just the app and dalvik folders there, some put much much more.
If it were me, i recon id be pulling teh battery at 10 mins.

do you have a 1gb partition on your sd card?
is the partition information for the rom correct?
are you using magldr or clk?

I have Tried wit a 2GB and a 1GB partition, I have Magldr 1.13, The Cwm size is also correct, 400mb for a 300mb rom.

amigo max said:
I have Tried wit a 2GB and a 1GB partition, I have Magldr 1.13, The Cwm size is also correct, 400mb for a 300mb rom.
Click to expand...
Click to collapse
You're absolutely sure the ROM you're trying to use is correct for the type of Android bootloader you have? (clk/magldr)
Did you check the MD5 sum of the rom.zip you downloaded? Maybe you got a bad download.
Did you wipe EVERYTHING? (full wipe, then in advanced, wipe dalvik and cache)
What method did you use to partition your sd card?

For now i Have followed the exact instructions from the DHD Desire rom, and it seems to work, I think the problem was wit the CWM recovery, I downloaded it from the Rom's page and it worked.

When I tried installing another Rom, I encountered the same prob, so I installed recovery again and it worked. Do I have to keep changing the recovery every time I put another Rom?
Sent from my HTC HD2 using XDA App

Yeah, some roms require different partition layouts, which are made when you flash CWM recovery.
If you are going from one rom to another and they both require the same partition layout, or if the new rom you're flashing requires a smaller system partition than your current rom, then you won't have to re-flash CWM. In that case, you'd just have to do a full wipe and then flash ur new rom.
The required/recommended CWM partition size is usually somewhere in the first few posts of the thread you download the rom from.
Sent from my HTC HD2 using XDA App

[Q] Restoring a backup

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

nandroid + flashing/restoring across roms

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