Related
I just purchased nexus one . I have been trying to root the phone and put Cyanogen recovery image 1.4 & Cyanogen 5.0.5 test3 rom.
So far i unlocked the bootloader (Says unlocked at top in fastboot now).get the little unlocked padlock every time the phone starts up
When attempting to flash the recovery image now i get: an error that says "Failed....(not allowed)". and if i retry the same command right after, it says its starting to flash but freezes. Same thing happens when trying the rom file too.
Attempting to unlock the bootloader again i get the error "... FAILED (unknown status code)".
What is going on and how can i get this to work? any help would be greatly appreciated.
CM Recovery is for the G1, not the N1.
Get this one: http://forum.xda-developers.com/showthread.php?t=611829
Instruction to install on first post.
mrandroid said:
CM Recovery is for the G1, not the N1.
Get this one: http://forum.xda-developers.com/showthread.php?t=611829
Instruction to install on first post.
Click to expand...
Click to collapse
yeah but what is the difference between the regular recovery and the cyanogen recovery? i first rooted with the standard recovery, then afterwards saw the cyanogen and flashed that recovery to my phone. things seem to still work the same, and previous nand backups can be restored via the cyanogen version. but what exactly is the difference?
i did notice that the cyanogen nand backup adds an extra file in there called "cache". what data is contained on that vs the regular recovery WITHOUT that cache file?
RogerPodacter said:
yeah but what is the difference between the regular recovery and the cyanogen recovery? i first rooted with the standard recovery, then afterwards saw the cyanogen and flashed that recovery to my phone. things seem to still work the same, and previous nand backups can be restored via the cyanogen version. but what exactly is the difference?
i did notice that the cyanogen nand backup adds an extra file in there called "cache". what data is contained on that vs the regular recovery WITHOUT that cache file?
Click to expand...
Click to collapse
Again, the CM Recovery is not made for the N1, switch to the other one. Better options, newer and fixed scripts for the N1 and froyo.
mrandroid said:
Again, the CM Recovery is not made for the N1, switch to the other one. Better options, newer and fixed scripts for the N1 and froyo.
Click to expand...
Click to collapse
Ok I'll go back to the standard recovery. But again, that link you posted specifically says nexus only only and has the cyanogen recovery for download right below the regular recovery. And the cyanogen one has more menu options than the regular recovery. So I'm confused what the difference is.
These recovery images go back to the very first custom one made for the G1/Dream - JF Recovery - by JesusFreke. Cyanogen started from that, made it better, and released it as CM Recovery. AmonRA took the CM recovery, and made it even better. The major difference is that the Amon recovery has more options, layered menus for easier navigation, and it uses new scripts for Nandroid and a2sd backup. For the moment, the only recovery images that work with Nexus One are Amon and the Clockwork recovery made by Koush. I've never used that so I don't know what's different there.
The Cache backup is essentially unnecessary because, as the name implies, it's just the volatile cache held on the partition while the phone is operational. Every time you turn the phone on and make changes, the cache changes. So you don't really need a backup for it because it can be remade when the phone turns on after restoring a backup.
Edit: That Cyanogen recovery link under the regular one is just a themed version of the AmonRa Recovery. The two are exactly the same, but the Cyan themed one has a different background and colour scheme. Just look at the two screenshots.
OK i understand, the cyanogen version is just the same thing as regular but has the cm "look" and feel to it.
Alternative CyanogenMOD version with Cyan colors and CM Logo
Click to expand...
Click to collapse
RogerPodacter said:
OK i understand, the cyanogen version is just the same thing as regular but has the cm "look" and feel to it.
Click to expand...
Click to collapse
Exactly right.
I've installed Amon Ra on my Nexus One as part of the process to get cyanogen running on it. I did the fastboot oem unlock + flash amon ra + manual update zip process.
Part of the reason was that for some reason I could never boot into clockwork recovery (yes I followed the wiki to the letter), and could only access the standard recovery (which doesn't allow custom roms, says the signature is invalid), the one in blue font. So I flashed amon ra instead and that worked fine.
Can I now flash back to clockwork, and even better, just do it via rom manager? Is there any risk or downside?
This is because I'm reading that amon ra doesn't have a wipe option, and that its better to wipe when you upgrade roms (or is that another fallacy or am I mis interpreting things)
cheers
1. If you didn't find and delete recovery-item-boot.p and install-recovery.sh, they will restore stock recovery when boot, regardless of what custom recovery you flashed.
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
Click to expand...
Click to collapse
2. You can change your recovery via ROM Manager, or manually. By the way, Amon RA Recovery has wipe option, of course. Where did you read that from?
LFact said:
1. If you didn't find and delete recovery-item-boot.p and install-recovery.sh, they will restore stock recovery when boot, regardless of what custom recovery you flashed.
2. You can change your recovery via ROM Manager, or manually. By the way, Amon RA Recovery has wipe option, of course. Where did you read that from?
Click to expand...
Click to collapse
1.) I'm pretty sure I'm booting into amon_ra, it has a nandroid backup option.
My attempt (fail) to install clockwork was exactly the same as how I successfully installed amon: via fastboot flash recovery /path/to/recovery-RA-nexus-v2.1.1-CM.img after unlocking the bootloader. I didn't manually find and delete those files you specified (wouldn't even know how TBH), just followed the Cyanogen wiki.
2.) Cool good to know. I suppose then there's no point in changing really. I was just reading posts and saw it referenced several times. Maybe they were out of date or early on in the piece.
Out of curiosity, is it worth wiping if you're just upgrading between the same version e.g. cyanogen 7.03 to future 7.04?
I much prefer Amon 2.2.1 It is 2.2.1 which is the latest version, not 2.1.1
Stay away from CW 3.+
Amon has a Data/Factory reset wipe for installing new roms, I wipe 5X with it. And, a Dalvik Cache and Cache options. Do those 5X also
If doing nightlies, just wipe the caches
Here is a link to a System Wipe zip you can flash from recovery. That is probably what they were taliking about. CW has that option and Amon will on the next version, I think.
http://forum.xda-developers.com/showthread.php?t=723844&page=1767
Ken
PS:
Otherwise, like mentioned you will default back to CW even if you flashed 2.2.1 thru Rom Manager on reboot.
Or, you can flash Amon thru fastboot and remove the two scripts mentioned above by LFact
Thanks mate I'll just keep using Amon
So you're saying to wipe I have to flash that zip, there's no way of just wiping it from the menu options before flashing the relevant ROM?
But in any event since I'm on CM7 I'll only be doing minor version bumps for the foreseeable future lol
I"m confused about the reboot issue: I can reboot into Amon at any stage. I haven't deleted those scripts. But you guys are telling me that unless I delete those scripts if I reboot I'll go back to stock recovery?
Sorry wrong thread.
Sent from my PC36100 using Tapatalk
@wintermute000
Yes, flash the system wipe zip from recovery like any zip. Only a few seconds. Hopefully , it will be in next Amon version.
Never an issue with Amon--
Get Quick System from market and use it to boot into recovery--exc app
Then you don't need Rom Mgr or CW--better that way
If you install Amon thru Fastboot or Terminal, it will not be erased on reboots--you still need to delete the two scripts mentioned before any rebooting
See post three on this link--DR has a flash able zip to do it--nandroid always first on this stuff
http://www.nexusoneforum.net/forum/...330-custom-recovery-wont-stick.html#post99962
wintermute000 said:
Thanks mate I'll just keep using Amon
I"m confused about the reboot issue: I can reboot into Amon at any stage. I haven't deleted those scripts. But you guys are telling me that unless I delete those scripts if I reboot I'll go back to stock recovery?
Click to expand...
Click to collapse
If you type
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
Click to expand...
Click to collapse
in terminal and it shows error message such as 'no file or directory', it means they were already removed. (I think ROM manager automatically remove them when flashing Clockwork recovery. When I changed to RA recovery, I found out those 2 files were gone)
If you're still curious about changing recovery, you can. I accomplished this yesterday by using Amon to flash a ROM with root access, then I downloaded CwM from the market. Installed the recovery using CwM. It's a simple process as long as you have root. As for going back to Amon, I haven't tried that.
Those files are gone (I didn't do rm, I just did basic ls in those directories). So I guess somehow during my Amon flashing it deleted it. Good to know.
Thanks for your patience all, I think I'll just stick to Amon then if I can just as easily wipe using a zip file if I need to. From what I've read I won't need to wipe anyway if I'm upgrading minor versions (i.e. CM7.03 to say 7.04 or nightly) and that's all I'm interested in doing. Hopefully by the time CM8 comes around I'll have taken the plunge on something dual core!!!
The whole reason I started investigating root/flash etc. was to give my N1 more legs until the price/performance point for the dual core phones gets to a better state, and its more than done that, I'm kicking myself for not doing it earlier. I guess once you're familiar with it then its a piece of cake, but I was reluctant for ages as I didn't want to screw up my PHONE (as opposed to say a tablet).
You don't need to remove those files since after you loaded Amon_RA, you installed CyanogenMod. Those files are used in Stock Android to replace whatever recovery you may have with the stock recovery on every boot.
I would still download the flashable zip that rugmankc linked to for formatting /system. Like I said in the CM forums, it normally isn't necessary when upgrading from minor versions, but sometimes it is the only thing you can do to fix a phone. I figure it is better to download it and never use it, then need it and having a hard time finding it.
+1 bass
@wintermute000,
I still wipe Dalvik Cache and Cache between nightlies. Seemed like the time or two I didn't do it, I had an issue.
The deal on using System Wipe if flashing new rom or if a lot of versions in between is:
When you flash a new rom it wipes system, but backs up some files from old rom first and reinstalls them as part of the new rom. After while things get cluttered, so a system wipe prolongs more serious issues. It has reduced the amount of times I need to do a complete wipe and/or sd card redos.
All Props to Temasek on this stuff
Ken
Greetings fellowmen!!
Recently i thought of rooting my nexus 1. So i did some research and found out that the easiest way to do it was by unlocking the bootloader installing a custom recovery (I did Amon Ra) and then wiping the data\factory settings and flashing the cm 7.1 zip. So i did all the above and there you go....I had an n1 running cm 7.1 smoothly but then after a few hours it starts to piss me of. The problem is that whenever i lock the homescreen with the power button and wake it up again it just displays the main homescreen and does nothing i cannot navigate to the left or right homescreen cannot open app drawer in short it just hung up there doing nothing. I had to take out the battery atleast 15 times. I rebooted my device and it kept on giving me the same problem.
So then i reflashed cm 7.1 by wiping the data and factory settings and installing it again. But still it gave me the same problem. So then i thought of flashing 7.0.3 version instead and surprisingly that works like a charm. So is it the mod thats buggy or is it my phone.
One more question. I have the stock 2.3.4 gingerbread rom which i got from here!!
Code:
http://forum.xda-developers.com/showthread.php?t=1061648
This one in particular-
GRK39F OTA (stock vanilla - odexed, unrooted):
MD5: 35C8B4B9FD22DD4CA19C5D026E74411D
So to install this rom do i have to install it the same way i did cm by wiping data/factory settings and then installing flash from zip or is there any other way to do it ?
Thanks in advance for taking out valuable time and reading my long problem!!
I am running the latest version of CM 7.1 that was released within the last week or so without any issues. Got it from here. http://download.cyanogenmod.com/?type=stable&device=passion
Before that I was running the RC for 7.1. One thing to try it wiping multiple times before flashing. I assume you are running Amon RA 2.2.1, which is the latest. I have never had a problem with that recovery, however I flashed my ROM with this recovery. So far I think I like it better than Clockwork and Amon.
http://forum.xda-developers.com/showthread.php?t=1291970
As for installing other ROMs yes you do flash them the same way you flashed CM.
So are you saying that it was the recovery that was causing the problem?
Yes I am using the latest Amon Ra 2.2.1 version.
I also got the rom from that link.
And can you explain whats the difference between all these recoveries?
Thanks for replying!
I am not saying it is the recovery, I highly doubt that is the problem. I was just comparing differences. There does not seem to be much difference in the recoveries for what you are trying to do. The recovery I am running is a fairly new one that I just wanted to test out. I do think I like it better than the others.
First thing I would do is wipe 3, 4 or 5 times before flashing. I have had rare occasions where a single wipe would not do it for me. Also have you verified the Checksum of the CM download? Does recovery say it installed successfully? I have also had error installing a ROM in recovery but then had the phone still load the ROM.
Yes i did check the md5 checksums and they match perfectly. Though i did wipe it out only one time so maybe that could be the problem. I think i should get clockworkmod and wipe it through that and then flash cm 7.1. Amon RA doesnt really give us the option of wiping the system partition. right?
Correct Amon Ra does not have an option to format system partition. It's recommend you also wipe system when coming from a different ROM.
Try this file by temasek's, format-signed.zip
http://www.mediafire.com/?8vbd13b440coxx6
just flash it in recovery and it will clean everything, now you can flash CM7.1 again
Are you sure you can't wipe the system with Amon? I remember having that option, but it's been several months since I have used that recovery. Kind of makes me want to flash it to find out.
Before flashing a different ROM I always wipe system, cache and dalvik cache. It is definitely important to wipe the system before flashing a new ROM. I'm sure that is where your problem lies.
No, ClockworkMod has it, but Amon_RA doesn't. Supposedly it is in the works for the next version, but that was a long time ago when I heard that (probably back when v3 for clockworkmod came out).
I did a nandroid backup and flashed the format zip file and then flashed cm 7.1 and its giving me the same problem!!
I had to restore and go back to 7.0.3
Why is this happening
Edit: I also wiped the dalvik cache and factory reset it also but still it just freezes!!
Any advise?
Have you tried downloading the file again maybe form another location I doubt this is the problem but sometimes it's something you don't expect.
You could try from here http://wiki.cyanogenmod.com/index.php?title=Latest_Version
But how does it matter I checked the md5 checksum and it matches!!
Why not stay on CM7.0.3 theres not much difference between the 2
if you dont want to i suggest to try to flash Clockwork recovery and do a full wipe then reflash CM7.1
But still I want to see how 7.1 is!
The main point here is to upgrade and not taking the alternative of staying at the older version!
Please guys any help would be appreciated!!
Doesn't CM7 need clockworkmod 3.x?? Try to flash CWM3.x over Amon if you can get your hands on the flashable zip or if you can get into a working rom, use romManager to switch from amon.
thealphamale05 said:
Doesn't CM7 need clockworkmod 3.x?? Try to flash CWM3.x over Amon if you can get your hands on the flashable zip or if you can get into a working rom, use romManager to switch from amon.
Click to expand...
Click to collapse
Make no different if you use amon Ra or CWM. I would definitely stay away from cwm 3.x or higher if you're using sd-ext
Looks like Ill have to stay with 7.0.3 there doesnt seem to be a solution!!
I have an AT&T Captivate with the official 2.2 on it. I'm rooted, but that's as far as I've gone with it. I'd like to try out this ROM: http://forum.xda-developers.com/showthread.php?t=1363760
From what I understand, I need to flash Clockwork Recovery for Captivate (MTD). But ROM Manager doesn't seem to be able to do that; it asks me if I have it already, which seems to mean that I'm supposed to get it from another source. I tried ignoring the warning as the thread I linked to says, but it just reboots into Samsung's recovery.
Where exactly can I find this recovery on my own?
Noo you just need clockwork recovery thats it. It will do the rest. Mind you this rom is in early dev, and I wouldn't recommend it for ppl that are starting out. I would recommend I9000 Gb ports or I897 leaks. Or a more stable GB AOSP like nightlies or the stable release from CyanogenMod team.
i totally agree with bass. go with something like cm7 or a leaked beta. in rom manager, when it asks if you have it already, say no, so you can install it. if you check my created threads i have a basic tool that will help you get to a leaked official captivate gngerbread rom as well as CWM. since you are on froyo you will need to use the one with the boot loaders so make sure you have a good battery charge. trust me, i speak from experience, its well worth the time it takes to wait for the charge. otherwise you end up with $500 paperweight.
I'm kinda set on that ICS one I linked to.
http://forum.xda-developers.com/showthread.php?t=1202673
if I start with that, can I then reboot into recovery and install the ICS rom I linked to?
You don't know how to use cwm or to root yet you want to try a rom in early dev that might give you a TON of issues. Don't get me wrong Im running build 10 and apart from random lag and under par battery life its been acting fine. Just saying you should be able to figure it out if you are thinking about that specific rom.
The Captivate is the only one that seems to require a special recovery for Cyanogen ROMs from what I understand. I want to make sure I'm doing this right.
and yes, I'd like to start with that ROM.
...actually, did you even read my post at all? I say right in the beginning I'm rooted, but you say that I don't know how to root?
Easy brother bass was not trying to low blow here. He was just making an observation from past experience. The early dev roms can be tricky little buggers to get loaded and running right. I too speak from experience I have had some nasty boot loops and or soft brick of my phone. I don't know about your past but if this is your first custom rom flash you may want to practice a bit before taking on an early stage rom.
Sent from my SGH-I897 using XDA App
popodopolus said:
Easy brother bass was not trying to low blow here. He was just making an observation from past experience. The early dev roms can be tricky little buggers to get loaded and running right. I too speak from experience I have had some nasty boot loops and or soft brick of my phone. I don't know about your past but if this is your first custom rom flash you may want to practice a bit before taking on an early stage rom.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
I agree, you should start off with something more stable to get used to flashing. The other day when build 10 came out I flashed just like I have been doing by performing a Dalvik and cache wipe then flashing the ROM and I ended up not getting past the splash screen. I had to take the phone back to stock, flash CM7 and then go back to ICS. For some reason in the process I lost 3 button combo so I had to use the ADB for reboots.
The point is take some time and learn from the beginning, don't just jump right in to the middle it will make your life easier in the long run.
Sent from this fully armed and operational battle station running ICS.
Sorry, it's just weird for him to say "you don't even know how to root" when that's the first thing I said about my phone...
I guess you've got a point. Maybe I'll start with something else.
If I wanted to start with CM7, could I start with this recovery: http://forum.xda-developers.com/showthread.php?t=1202673
I would recommend ODIN, its much much easier. First off does your phone 3 button combos work? If not I would recommend flashing a 1 click GB rom w/ bootloaders. and then use a kernel like Boog's to flash cwm. If your 3 button works just flash any kernel with cwm and flash from that. In both cases make sure you have all the necessary .zips in your internal SD card.
The simple answer is you need to replace your stock recovery with a modified 2e or 3e recovery that clockworkmod is compatible with.
Since you are on 2.1, I believe you will need the 2e, but it may be easier for you to Odin to froyo and use a 3e recovery instead.
heres a video on how to do it.
here is the link for a modded 3e recovery file that you can download. that should take care of your problem if not let me know.
make sure to follow directions from video. after replacing this recovery file you should be able to flash clockworkmod thru rom manager just make sure to boot into recovery from rom manager if the stock recovery still shows up you may have to select the option to update packages from stock recovery once or twice to get cwm to take.
these directions have been used on both my captivate and my buddy's fascinate with no problems.
popodopolus said:
The simple answer is you need to replace your stock recovery with a modified 2e or 3e recovery that clockworkmod is compatible with.
Since you are on 2.1, I believe you will need the 2e, but it may be easier for you to Odin to froyo and use a 3e recovery instead.
heres a video on how to do it.
here is the link for a modded 3e recovery file that you can download. that should take care of your problem if not let me know.
make sure to follow directions from video. after replacing this recovery file you should be able to flash clockworkmod thru rom manager just make sure to boot into recovery from rom manager if the stock recovery still shows up you may have to select the option to update packages from stock recovery once or twice to get cwm to take.
these directions have been used on both my captivate and my buddy's fascinate with no problems.
Click to expand...
Click to collapse
Wtf?
2.1 didn't require anything special for recovery. Update.Zip on sdcard and you are good. You damn sure don't replace recovery2e with anything else and it damn sure is not easier to use recovery3e.
Sent from my SAMSUNG-SGH-I727
popodopolus said:
The simple answer is you need to replace your stock recovery with a modified 2e or 3e recovery that clockworkmod is compatible with.
Since you are on 2.1, I believe you will need the 2e, but it may be easier for you to Odin to froyo and use a 3e recovery instead.
heres a video on how to do it.
here is the link for a modded 3e recovery file that you can download. that should take care of your problem if not let me know.
make sure to follow directions from video. after replacing this recovery file you should be able to flash clockworkmod thru rom manager just make sure to boot into recovery from rom manager if the stock recovery still shows up you may have to select the option to update packages from stock recovery once or twice to get cwm to take.
these directions have been used on both my captivate and my buddy's fascinate with no problems.
Click to expand...
Click to collapse
Uh no.... If he is on 2.1 and iss on 2e why in God's name would you want to flash 3e? In the end of the day why the hell don't you just flash a kernel with it baked in? (if you really want to flash something that is.)
Also DO NOT,by all that is holy, use Rom Manager. Its useless on our Galaxy S phones (not knocking on the dev, its brilliant for HTC's and Motorolas).
Sorry I miss typed he is on froyo so the links that I gave him will get the job done
Sent from my SGH-I897 using XDA App
If he is on 2.2 its better for him to just flash a kernel with it baked. Gives him CWM + all the great tweaks.
Hey forum, pretty much a noob (not even 10 posts) I would like to get off my stock AT&T Gingerbread rom (KK4 2.3.5) and I keep looking through the posts for a lil explanation, can't find any. So I'm hesitant to flash roms without properly knowing what is actually going on within. Essentially I would just like to test the water first by rooting so I could get rid of the AT&T crap, and possibly progress to a full-on custom rom. If there are any devs, or passers-by that could assist, I would be more than grateful.
I suppose comparing it to regular PC terms would help best, as i feel I am somewhat savvy with PC's.
Root can be acquired through the [APP]SuperOneClick, or gained through [MOD] FuguRoot: root _any_ stock SGS ROM safely (froyo, GB) or by means of Flashing a Custom Rom (all have Root). See this 【Guide】How To flash Captivate ROMs from Stock (inc. Gingerbread ROMs) or U could flash a Developer's Kernel that has the CWM Recovery baked in and the option to install Root through said recovery (Corn Kernel is one that is based on KK4. I recommend v6.03 because it is very stable).
And be sure to read the Stickied Threads View attachment 868387 in the Captivate General, Q & A, and Delelopment Forums. That will prove to be most helpful.
Very cool. Now i suppose I'm being a pansy about this, but you seem pretty knowledgeable; if (rather when) I take the plunge to a new rom, will that wipe the whole card (which is where I'm assuming that the system is mounted), including any apps that I have gotten, and/or erase the SIM card (I hope not)?
Yes it wipes apps, although those aren't stored in /system they're in /data but a full wipe ROM will clear data. Use titanium backup to backup your apps, move contacts to Sim card or backup to your gmail.
It will not touch your Sim card.
When I attempt to root using SOC it locks up at step 7 (shell root), it freezes. Of any assistance, I look at my task panel, it runs 2 instances of adb.
Sent from my SAMSUNG-SGH-I897 using XDA App
Use the FuguRoot method or just use Odin3 v1.83 to flash the .tar v6.03 of Corn Kernel. The .tar file goes in the PDA slot of the Odin.
Open Odin 1st, Select the PDA tab, Navigate to the .tar kernel (that u sould have downloaded) Connect ur phone to ur pc in Download mode and once Odin recognizes it, select Start. Kernel will get installed and phone will reboot. Afterwards use button combo to get into CWM Recovery (hold volume up and volume down and power button at the same time until u see the att splash screen then release the buttons). U r now in cwm recovery and can install root from there. Look under Reformatting, tweaks and more. There u will find the option to install root.
Sent by XDA Premium App
4-2ndtwin, I would like to verbally thank you, in addition to the "digital" thanks given already, I'm running the Corn Kernel right now, and from what I can see, it's a re-packaged KK4 with CwM to allow installation of root from the Bootloader menu. Now what I'm wondering, is what is the difference between the available kernel's for i897 (Captivate), more specifically those running the 2.3.5 kernel, e.g. corn kernel is re-packaged and does not have VooDoo sound, in PC terms could that be equated to a specific driver for the sound processor vice a generic driver included in the kernel?
Secondarily, just prior to appying root, I backed up everything using Nandroid, is that essentially a 1-to-1 image of what's on the rom?
Third(arily) , does Ti Backup save apps in such a state that I can move the .apk's to my pc desktop, install a custom ROM w/wipe, and re-install the apps as if they were there the entire time?
I appreciate any help.
Voodoo sounds is kinda like that, its a module compiled in the kernel that allows the tweaking of audio levels by the user with an app called voodoo control.
A nandroid is a system image yes, but it is not 1 for 1. They do not contain kernels or modems. Just the firmware and user settings and stuff. So, if you were to flash a different ROM, you would have to flash back to what the backup was made on, then restore the nandroid and it'll be like you never flashed anything.
Tibu backs up the apps and their data top a folder in your sdcard called "titanium backup" just move that whole folder back and forth and it'll work fine. Hell you can even put that folder in a different phone and restore those backups
The reason I was inquiring about Voodoo sound is (call me crazy) the volume reference has gone up a few notches since Froyo i.e. the lowest earpiece volume is twice what it was with Froyo. It's too bad there isn't a "Patchable" kernel that one could add that into.
I hate to admit this, but I always get confused at the term SD Card, as i usually think of dynamic storage that can be removed, not a static, soldered-to-mainboard storage that it is. So if I got a ROM that wiped the entire static storage, wouldn't I also lose the backups that Nandroid made?
Sdcard reffers to the /sdcard partition on the internal sdcard.
A ROM does not wipe this partition, that's where they are flAshed from, it can't wipe itself from existence and still continue the flash.