Which ROM with apps2sd+? - Desire General

I have currently got a R1 rom with apps2sd on it but would like a ROM with apps2sd+ to save internal memory.
I have narrowed it down to 2 roms,
Pays-ROM Desire Sense v1.6 Dalvik+A2SD (RockSolid)+(BraveSoul OC)[05/19/10]
or
17/May r3 - MoDaCo Custom ROM
Im not to sure which one to go for. The requirements im after is obviously apps2sd+ and is the most similar to the standard HTD desre ROM.
Thanks,

Depending on the options you choose in the kitchen you can get the Modaco ROM to be pretty much the same as HTC Sense. I'm running a r3 MCR with A2SD+ and ADW Launcher on top and everything's running great.

Will changing the ROM wipe everything from the phone or will it still be there?
Finally, when installing the ROM with a2sd+, will it move the dalvik cache automatically to the SD or will i have to do it?

It's definetly recommended to do a FULL wipe before flashing a ROM. Just be as thorough as you can possibly be to avoid issues or even just having to flash again. Don't want to scare you but some people did brick their USB port while flashing. How this exactly happens isn't really clear but i always just do that bit extra to avoid issues.
So, you can use titanium backup to backup all your apps+appdata and also systemdata, then in recovery you can also do a nandroid backup which will backup your full system.
If flash is succesfull you can restore your backups with titanium backup again. Don't try to restore HTC stuff when it's not included in the new ROM.
If flashing is not succesful or you encounter to many issues you can always restore your nandroid backup. I tried to make a nandroid+ext partition backup but that didn't work somehow so i always just copy the whole card to my pc before doing anything.

Related

[Q]ROM backup question.

Hey folks, I have done my homework and I have a fair understanding of how to flash ROMs and radios onto the Desire. However, I just need a little help with the Nandroid backup.
I have backed up my Current MoDaCo R8 ROM (I bought my Desire Rooted with R8 installed) I want to install Cyanogen 6.0.2, however my rather verbose question is, if I am not happy with Cyanogen (Or any other ROM for that matter) can I use the Nandroid backup to reinstall my previous ROM in it's entirety once Cyanogen is installed? Or is it used just as a failsafe for a bad ROM flash? I am a bit clueless.
Thanks in advance any enlightenment!
Yes you can, I have been testing different ROMs and using nandroid backups to go back from one to another and it restored the ROM with the whole configuration
Just in case.. do a full wipe before restoring a backup
Thanks for the info.
What about the SD card? I have already made a back up of my R8 SD card, is it wise to wipe it as you go from ROM to ROM? I notice it throws all kind of rubbish in a plethora of different folders, not at all like Windows Mobile, I would think it is good idea to back up and wipe, am I right?

[Q] Best way of updating Redux?

I've installed Redux and enjoyed it on my phone for over a month now. However, I see there is a newer version out. What is the best way of updating (bearing in mind I've got quite a few apps that I don't want to install)?
TIA
You can just flash the new Redux version with the Rom Manager or with the Recovery. You dont have to wipe because you're already on Redux.
Nothing would be deleted. But it's helpfull to do a nandroid backup (a nandroid backup will backup everything on your phone (Apps, Data, Settings,...)) with Rom Manager or Recovery if something goes wrong with the update.

How do I change to a different ROM?

A total noob question but that's because I'm a noob. Anyway I'm currently using CynogenMod7, but I want to try a diffrent ROM. What do I have to do?
All the info you need to do that is here
Okay but would I have to format my SD card or partition it?
How would I keep my old apps and app data?
Thanks
Tajio said:
Okay but would I have to format my SD card or partition it?
How would I keep my old apps and app data?
Thanks
Click to expand...
Click to collapse
You dont need to format SD Card (some ROM's require EXT partition, if you dont have it then you might need to repartition it), to keep apps and app data use Titanium Backup.
Backup apps using Titanium Backup
Backup contacts
Boot into recovery
Perform Nandroid backup
Wipe/factory reset
Install new ROM from zip
Sent from my CM7.1 Desire using XDA Premium App
some basic things before flashing ROMs
Depends on what ROM you're trying to flash. Some ROMs don't require partitioning your SD card. However, ROMs that feature A2SD+, Data2SD, Data2Whatever or Data2Ext will require that you make 2 or 3 partitions. Those 4 scripts are for people who have tons of apps and cannot be served by the stock phone memory.
Safest way to enjoy flashing ROMs is to:
a) save all the stuff in your SD Card onto your computer or another storage device
b) sync all your contacts into a Google account. If you don't have one, make one. You'll find it very convenient to sync back all contacts everytime you flash a new ROM
c) use MyBackup Root or Titanium Backup; they can both save apps for later reinstatement, include settings and data, like your Angry Birds score. Personally, Titanium Backup is much better than MyBackup Root. Go buy the pro version, it works even better.
d) remember to make a Nandroid backup in recovery. Be aware, though, that when you make a Nandroid backup in ClockworkMod and in the future decide to flash Amon_Ra or another recovery, those cannot restore the nandroid backup that CWM did. Amon_Ra nandroid backup can only be restored by Amon_Ra recovery, likewise with other recoveries. So the first step to do after flashing a new recovery is to make another nandroid backup, in case of trouble.
e) remember the golden rule of safe flashing: always wear a condom. Ooops. I meant, wipe data, cache and Dalvik-cache. Many problems with hanging or bootloops can be traced to not doing the 3 wipes.
Alright thanks everyone!
Can somebody post a link how to root desire i have one and is running stock
want change it. Sorry for hijacking the thread as i dint wanted to start a new one for this.
http://forum.xda-developers.com/showthread.php?t=1016084
There's a search feature also
Sent from my CM7.1 Desire using XDA Premium App
noob here too and this is exactly what I was looking for.
first root a few days ago and flashed GingerVillain 2.7 but was wondering how to go about flashing to a new rom (possibly cyanogen 7).
this answered my question.
thanks to all for the thread.
zedmarcus said:
noob here too and this is exactly what I was looking for.
first root a few days ago and flashed GingerVillain 2.7 but was wondering how to go about flashing to a new rom (possibly cyanogen 7).
this answered my question.
thanks to all for the thread.
Click to expand...
Click to collapse
Go into recovery, full wipe/factory reset + dalvik cache wipe and flash new ROM.
When you flash CM7 dont forget to also flash google apps (look in first post)

[Q] Force closes long lag times, other problems so un-root/re-root or something else?

So, I have been having some major problems with my phone. Tons of force closes, major lag times and things like that. I have tried a handful of different ROMs, including CM7, the nightlys, Miui and a few others. I hear great stories about people and rooting and I want to be one of them. I am tired of all the hassles. So, when talking to someone in the office who has had no issues with his Droid 2, he suggested, and said he has read, the best thing to do is go back to stock, unroot, as they will remove all possible conflicting files that could be causing problems. Then, re-root, and install whatever.
Any thoughts on that? Generally, my process for installing a new ROM, I boot into recovery manually, clean cache, clean Dalvik, then install ROM. Then, I restore apps and data from Titanium and restore the Nandroid from Rom Manager. The past couple times, I have done the factory reset, but eventually, a day or 2, it goes back to the same problems. Maybe, I should just try it without the restoring the Nandroid (even though it is a backup from when there was no problems) and the app data from Titanium. I assume, you know what happens when you assume, that both the Nandroid and Titanium backups are clean as I backed up when I was having no issues.
So, any thoughts here? Unroot, then re-root or is there something else I should try to wipe everything clean to solve the problems? Currently, on the original Droid Incredible (got it on the release day, so the first screen), running 2.2 when I rooted, currently on Miui 1.9.16, but just installed it 10 minutes ago and was running the Cyanogen nightly's before hand..
Thanks in advance
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
Try not restoring apps and data from Titanium, as restoring the app is okay, but restoring data can cause unwanted things to happen more times than not.
When you say restore nandroid from ROM Manager, what do you mean here? A nandroid is backing up your ROM via ROM Manager, which gets stored to your clockworkmod/backups folder...you shouldn't be pulling anything from that...
If you flash the RUU to return to stock and re-root, make sure you use the 2.2 RUU. If you use the 2.3, you need to be s-off to get rooted again. If you use the 2.3 RUU and you're s-on, no root for you...come back one year.
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
As for Titanium, I restore apps with data all the time, but system data should almost never be restored as it's OS and app version specific. Basically, if it's green, it's safe. If it's red, don't mess with it. If it's white, like a user app, app and data are usually safe to restore.
ROM Manager is a bigger pain in the ass than it's worth and is useless for anything more than flashing a new recovery. If my recovery is working reliably, I never install ROM manager. Most devs will tell you to never flash with ROM manager anyways. Any function that ROM Manager performs can be performed in recovery in a safer, more reliable fashion.
loonatik78 said:
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
As for Titanium, I restore apps with data all the time, but system data should almost never be restored as it's OS and app version specific. Basically, if it's green, it's safe. If it's red, don't mess with it. If it's white, like a user app, app and data are usually safe to restore.
ROM Manager is a bigger pain in the ass than it's worth and is useless for anything more than flashing a new recovery. If my recovery is working reliably, I never install ROM manager. Most devs will tell you to never flash with ROM manager anyways. Any function that ROM Manager performs can be performed in recovery in a safer, more reliable fashion.
Click to expand...
Click to collapse
Thanks for the correction, I forgot to put system in there...restoring system data is not good.
+1 on ROM Manager issues, always get a zip file of the ROM, and flash through recovery.
RMarkwald said:
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
When you say restore nandroid from ROM Manager, what do you mean here? A nandroid is backing up your ROM via ROM Manager, which gets stored to your clockworkmod/backups folder...you shouldn't be pulling anything from that....
Click to expand...
Click to collapse
That is pretty much what I do, except for the Mounts and Storage parts.
For the Nandroid part, maybe I have my terminology mixed up. I do a restore from Rom Manager...which I thought was called the Nandroid backup. It seems to me, that it makes sure the launcher and things are set up right.
loonatik78 said:
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
Click to expand...
Click to collapse
I rarely use the ROM Manager to do anything, just restore (what I thought was called the Nandroid) to make the launcher the way things were..
But it seems like that is my problem. I am installed the new ROM, then just restoring a back up of all the problems. DUH.. Guess I should try it all without restoring anything from the ROM Manager and see how it all works. That will be my project tonight..
Thanks
MikeDaub said:
That is pretty much what I do, except for the Mounts and Storage parts.
For the Nandroid part, maybe I have my terminology mixed up. I do a restore from Rom Manager...which I thought was called the Nandroid backup. It seems to me, that it makes sure the launcher and things are set up right.
I rarely use the ROM Manager to do anything, just restore (what I thought was called the Nandroid) to make the launcher the way things were..
But it seems like that is my problem. I am installed the new ROM, then just restoring a back up of all the problems. DUH.. Guess I should try it all without restoring anything from the ROM Manager and see how it all works. That will be my project tonight..
Thanks
Click to expand...
Click to collapse
If you want to restore your launcher, try it through Titanium Backup. If that doesn't do it, and I can't promise you it will work correctly, you're probably SOL on restoring a launcher unless some other backup app does the job better.
loonatik78 said:
If you want to restore your launcher, try it through Titanium Backup. If that doesn't do it, and I can't promise you it will work correctly, you're probably SOL on restoring a launcher unless some other backup app does the job better.
Click to expand...
Click to collapse
I am fine with not restoring it, I just thought "that is what you should do".
I don't venture too far from the regular settings, so it isn't a pain to do, just thought I should...
RMarkwald said:
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
Click to expand...
Click to collapse
One more quick question since I am thinking of it....is this same process if doing nightly updates from Cyanogen, or just is I change from say, Cyanogen to Miui or something??
Thanks again for all the help..
MikeDaub said:
One more quick question since I am thinking of it....is this same process if doing nightly updates from Cyanogen, or just is I change from say, Cyanogen to Miui or something??
Thanks again for all the help..
Click to expand...
Click to collapse
Generally, CM nightlies can be flashed over top of each other without a wipe since the vast majority of the code is identical. However, if an issue crops up, a wipe and flash might be a good thing to try. Probably won't help though, since nightlies, by definition, are experimental.
Always wipe and flash when moving from one ROM type to another.
loonatik78 said:
Generally, CM nightlies can be flashed over top of each other without a wipe since the vast majority of the code is identical. However, if an issue crops up, a wipe and flash might be a good thing to try. Probably won't help though, since nightlies, by definition, are experimental.
Always wipe and flash when moving from one ROM type to another.
Click to expand...
Click to collapse
That's kinda what I figured, but I thought it was worth asking so I don't completely wipe the whole thing every time I install an update. The nightly I am on now seems to be working, so the new plan is keep whats working until it doesn't work anymore, or some major update comes along..
Thanks again for the help. I really appreciate it.
If the issue continues you can try copying everything off of your SD card to your PC and reformatting your SD card. Remember to use FAT32 format. Then copy everything back to your SD card. I've read threads were this helped the force close issues for many people - Just a thought.
jackbtha1 said:
If the issue continues you can try copying everything off of your SD card to your PC and reformatting your SD card. Remember to use FAT32 format. Then copy everything back to your SD card. I've read threads were this helped the force close issues for many people - Just a thought.
Click to expand...
Click to collapse
Certainly worth a thought. The card that is in it now came from a different phone. I am pretty sure I formatted it when I first plugged it in, but it can't hurt to try...
Thanks

Planning to S-OFF, some questions before I do

So, I'm planning to finally S-OFF, mainly for the extra internal storage, and the extra speed since I won't be needing my ext3 parition any longer, so just to get some things straight -
1) I am currently on the latest Oxygen ROM, is it OK to S-OFF with this ROM?
2) I've made a nandroid backup of my ROM for restore, thing is, once I re-partition without an sd-ext, what happens when restoring the nandroid? Because when restoring, it needs to restore sd-ext... What do I need to do?
Thanks
As far as I know, Oxygen has a built in a2sd enabled when it sees that you have an EXT partition and might mess up Alpharev's (and or Revolutionary's) S-off process accourding to their site. I suggest you flash CM7 rom temporarily then S-Off with this installed since natively it doesn't support A2SD.
I'm not sure about the 2nd question. My logic tells me that I leave the ext, and do a nandrestore because it will obviously look for an ext partition to flash the data files back. The problem is once, restored and rebooted I don't know if there is a command or zip file you can flash to undo the a2sd and transfer the data from the ext to the data partition of the phone.
It would be better to go do a fresh reinstall of the rom and use titanium backup to restore your apps back.
Thanks, I probably will do the long TB restore process.
Re. the ROM issue - Will flashing Leedroid 2.5.0 Froyo ROM be good enough? As it seems to be pretty stock-ish.
Quoting Alpharev.nl
Requirements:
The only requirement right now is that the ROM you're running is rooted.
As techniques such as 'data2ext' have been popping up, these might disturb our finely-tuned flashing process.
Please revert to a rooted stock ROM if possible. Your /data partition is used for temporary storage of important files.
Click to expand...
Click to collapse
For my understanding as long as the ROM doesn't use data2ext, or 'anything'2ext out of the box it's good to go. I've S-off with Cyanogenmod rom on my phone so I can only speak from what I experienced.

Categories

Resources