Database Develop

Noob root question

after rooting and flashing ROMS, im confused on somethings. When flashing a new ROM do you ALWAYS have to wipe? Also, when you make a Nandroid back up, wipe and flash a new ROM, can you restore from that backup so you dont have to download all your apps//set up your screens all over again? Please help.

If you are switching to a completely new rom, then yes, you have to do a complete wipe. If you are upgrading a rom, adding mods or something similar then you don't need to do a data wipe. If you are switching from a rom that uses apps2sd from one that uses it you should probably wipe your ext partition as well.
To answer your second question, a nandroid backup backs up EVERYTHING on your phone, so using a nandroid restore will knock out your new rom and put everything back the way it was, including apps and settings. If you nandroid back from your new rom (lets say your phone gets stuck in a boot-loop or something...) you should do a data wipe and wipe ext partition, then nandroid.

one-of-four said:
If you are switching to a completely new rom, then yes, you have to do a complete wipe. If you are upgrading a rom, adding mods or something similar then you don't need to do a data wipe. If you are switching from a rom that uses apps2sd from one that uses it you should probably wipe your ext partition as well.
To answer your second question, a nandroid backup backs up EVERYTHING on your phone, so using a nandroid restore will knock out your new rom and put everything back the way it was, including apps and settings. If you nandroid back from your new rom (lets say your phone gets stuck in a boot-loop or something...) you should do a data wipe and wipe ext partition, then nandroid.
Click to expand...
Click to collapse
what does wipe ext partition wipe

also...
I want to use stock Android 2.1 ROM but want to use SetCPU to overclock. I tried flashing this kernel: http://forum.xda-developers.com/showthread.php?t=690238 but was stuck on the white/green HTC Screen. I then tried this kernel: http://forum.androidcentral.com/162759-post49.html and it got rid of super user permission so I couldnt use SetCPU. Is there another kernel I can use? If so can you PLEASE provide download link? One more thing, how do I compile this: http://forum.xda-developers.com/show...ghlight=kernel

shamrock11 said:
what does wipe ext partition wipe
Click to expand...
Click to collapse
It has your apps2sd info in it, hence wiping before changing roms because most use different versions of a2sd.

one-of-four said:
It has your apps2sd info in it, hence wiping before changing roms because most use different versions of a2sd.
Click to expand...
Click to collapse
I want to use stock Android 2.1 ROM but want to use SetCPU to overclock. I tried flashing this kernel: http://forum.xda-developers.com/showthread.php?t=690238 but was stuck on the white/green HTC Screen. I then tried this kernel: http://forum.androidcentral.com/162759-post49.html and it got rid of super user permission so I couldnt use SetCPU. Is there another kernel I can use? If so can you PLEASE provide download link? One more thing, how do I compile this: http://forum.xda-developers.com/show...ghlight=kernel ?

shamrock11 said:
I want to use stock Android 2.1 ROM but want to use SetCPU to overclock. I tried flashing this kernel: http://forum.xda-developers.com/showthread.php?t=690238 but was stuck on the white/green HTC Screen. I then tried this kernel: http://forum.androidcentral.com/162759-post49.html and it got rid of super user permission so I couldnt use SetCPU. Is there another kernel I can use? If so can you PLEASE provide download link? One more thing, how do I compile this: http://forum.xda-developers.com/show...ghlight=kernel
Click to expand...
Click to collapse
Ok... I'll give you what info I can, but I'm somewhat new to this myself... the first kernel you tried to flash has to be used in tandem with the rom listed at the top of the thread (darchdroid...) the second needs to be used with damage control's rom. I don't understand why you lost su permissions by flashing the second one, but again I'm new to this.
I hope you made a nandroid backup (always do this, otherwise some people around here will flame you...) I would restore, try installing the rom for the kernel you want to use and then re-flash it.
Something you might like is freshtoast (check: http://geekfor.me/new-release/fresh-toast-v21/) it has a stable rom (fresh 2.1.x) and all the overclocking goodies you're looking for. That way you won't break your phone / lose root in the process.
P.S. your link is broken for your last question, so I can't answer it

one-of-four said:
Ok... I'll give you what info I can, but I'm somewhat new to this myself... the first kernel you tried to flash has to be used in tandem with the rom listed at the top of the thread (darchdroid...) the second needs to be used with damage control's rom. I don't understand why you lost su permissions by flashing the second one, but again I'm new to this.
I hope you made a nandroid backup (always do this, otherwise some people around here will flame you...) I would restore, try installing the rom for the kernel you want to use and then re-flash it.
Something you might like is freshtoast (check: http://geekfor.me/new-release/fresh-toast-v21/) it has a stable rom (fresh 2.1.x) and all the overclocking goodies you're looking for. That way you won't break your phone / lose root in the process.
P.S. your link is broken for your last question, so I can't answer it
Click to expand...
Click to collapse
I don't want to use a rom. I was told I can overclock if I use a custom kernel. Which kernel should I download from the second link and heres the last link: http://forum.xda-developers.com/showthread.php?t=684838&highlight=kernel

Sorry for the delay... long day(s) at work!
For your kernel problems, please read this guide: http://forum.xda-developers.com/showthread.php?t=622916
It gives you step by step instructions on how to compile and install (probably the wrong term, but whatever...) the kernel you want.
In order to use setCPU you'll need a custom kernel, the CDMA Hero doesn't support it straight out of root.
This thread seems like it may contain your answer: http://forum.xda-developers.com/showthread.php?t=699792
I also highly recommend heading to following link, it has tons of guides and will answer most of your questions: http://forum.xda-developers.com/showpost.php?p=6738713&postcount=1
Hope this helps, but as far as more in-depth kernel questions, you'll need to find someone else to ask, I'm all out of ideas

[RECOVERY][UNOFFICIAL]Clockworkmod 3 series

Wiping and backup problems have been fixed in CWM3 > 3.0.0.5. If you had trouble before, try again with ROM Manager. Try to flash the recovery at least twice before giving up, or use an alternate method below.
Ensure that "wipe recovery" option in ROM Manager settings is checked. There is no good reason to not have this checked. It should probably be the default. This will not affect your backups.
3.0.0.8 has fixed the SLCD problems. If you get the black screen with white bars, upgrade to 3.0.0.8.
Koush's official answer as to why you can't flash old .zip files with 3x.
Why you should upgrade to CWM 3 series from 2 series
CWM2 IS NO LONGER SUPPORTED AND MAY BREAK AT ANY TIME
ROM Manager won't work with 2 series anymore
support for journaling filesystems. Your data is safer.
pretty orange color
power down from recovery
better partitioning support
may be required for Cyanogenmod in the future. It is not required for the inc as of now.
Why you should not upgrade to CWM3 series
Fear of messing with recovery is not a good excuse
You want to install ROMs from ROM developers that use 2 year old technology and have refused to upgrade their zipping mechanisms (put pressure on them to change their installation scripts)
You like old ROMs that haven't been updated in ages
You are one of the few that the new recoveries don't work on. Ask and someone can probably help you get through this.
WHERE TO GET OLD VERSIONS OF CLOCKWORKMOD:
http://mirror1.kanged.net/recoveries/ - contains img files for all old versions
*http://dougpiston.com/?page_id=85 - contains PB31IMG for flashing through HBOOT, including 2.5.12 and 3.0.0.8. This is the easiest way to manually update recovery.
HOW TO INSTALL IMG FILES
***YOU SHOULD INSTALL THROUGH ROM MANGER IF AT ALL POSSIBLE. TRY TWICE IF IT DOESN'T WORK ON THE FIRST TRY***
Rename the image file you're interested in to recovery.img
OPTION1: ADB
Code:
C:\YOUR_ADB_DIR\>adb shell
$su
$/system/bin/flash_image recovery /sdcard/recovery.img
OPTION2: Android Terminal from phone
Copy the recovery.img to the root of your sd card.
Code:
$su
$/system/bin/flash_image recovery /sdcard/recovery.img
OPTION3: Use PB31IMG.zip
Download specific recoveries from dougpiston.com
If it is not available elsewhere, oll your own PB31IMG.zip
This is not as hard as you think. Download any recovery PB31IMG.zip, such as the one attached to this thread. Replace the recovery.img in the zip file with the one of the desired CWM recovery. Rename to PB31IMG.zip. Place in root of your SDCARD. Reboot into HBOOT. Install.
What to do if you have trouble with CWM3
Check partitions for errors
Try installing through ROM Manager, or installing through one of the alternate methods listed above
make sure wipe recovery is checked in ROM Manager settings.
make sure you have the latest version of ROM Manager. Check in the market.
How to manually wipe recovery partition.
The utility is present in CM7 builds. I cannot vouch for other ROMs. This can also be done easily through fastboot mechanisms, but afaik fastboot is not available for the incredible because there are not leaked engineering HBOOTs.
This should never need to be done except in extreme circumstances.
Code:
$su
$/system/bin/erase_image recovery
How to get into recovery manually w/out ROM Manager
Shut down your phone. Hold down volume down. Press power, keeping volume down held. This is HBOOT. Scroll down to recovery and push the power button again.
HTC Incredible Amend vs. Edify: How to get old ROMs working with CWMv3
Amend and Edify are scripting languages used to write the installation routines for .zip files, including ROMs. Amend is quite old, from the cupcake days, and as such does not have features necessary for modern ROMs. To simplify development, Koush removed amend support with the advent of CWMv3. He had announced that he was going to do this for months. Nonetheless, some older ROMs that are not actively developed anymore may be desirable, and many of these do not use the more modern edify scripting. There is a thread here on how to easily convert amend scripts to edify using amend2edify: http://forum.xda-developers.com/showthread.php?t=903598.
Other sources for help
IRC
#cyanogenmod or #koush - it is recommended you try the solutions noted in this thread first. Self initiative is important, but seek help if you need it.
Who are the people behind CWM:
koush is the primary developer, slayher and CUViper help adapt it to the incredible, I'm sure many others.
How to build Clockworkmod yourself:
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
EDIT 2/27/11: This thread used to contain info regarding a custom build of CWM3006. It is still attached to this thread, but koush has upgraded CWM to 3008 which contains the 3006 fixes and more.
Click to expand...
Click to collapse

Thank you I haven't really had any problems with 3.0.0.5, but I've seen a lot who have. Maybe this fixes some of the wiping bugs people were having?

BrettApple said:
Thank you I haven't really had any problems with 3.0.0.5, but I've seen a lot who have. Maybe this fixes some of the wiping bugs people were having?
Click to expand...
Click to collapse
It is really odd, as I can install this version and backup/restore fine, then switch back to 3.0.0.5 and backup locks up consistently.
Its true re: the wiping bugs. It seems there's a lot more noise about the 3 series CWM than the 2 series, although I wonder if its just a lot more people are installing it and not quite understanding how cwm/hboot/cm7 interact. Hard to tease it apart.
I'm talking to koush and trying to get him to recompile it and make it official, regardless.

I tried the above CWR and my recovery screen is all black with white boarder on each sides.

meazz1 said:
I tried the above CWR and my recovery screen is all black with white boarder on each sides.
Click to expand...
Click to collapse
Thats quite odd. Try reflashing a working recovery and then back to this one?
What ROM/Radio/Phone (inc slcd or amoled)?
You can also extract the recovery.img out of the zip file and flash it with adb or flash_image.
Let me know please, I'll pull it down if there's consistent problems.

dont pull it booted on my device and ROM.... i'll do some extensive testing and report back

Sounds like this is for AMOLED only
Side note, I looked at an SLCD Incredible today. Noticeable difference in screens. I will say that AMOLED is much brighter and produces better color than SLCD, but SLCD wins hands down in crispness.

ok
1. doesnt show proper version in rom manager
2. will not flash rom via rom manager... probably hook issue
3. works fine in recovery mode
imo if it dont work via rom manager its kind of a deal breaker for me... alot of my users want to use it as well as be able to flashover without having major issues
right now with 3.0.0.5 if you flash via rom manager without a full wipe... chances are... you'll end up wiping and reinstalling because of fc issues

Flashed fine here. In the process of making a back up.
I'm diggin the power-off feature.
I only use RM to DL roms, flashing within RM only breaks ****.
Backup sucessfully made.

lllboredlll said:
ok
1. doesnt show proper version in rom manager
2. will not flash rom via rom manager... probably hook issue
3. works fine in recovery mode
Click to expand...
Click to collapse
1) I believe if a recovery doesn't show up in the clockworkmod available recoveries, it will not show the proper ROM Manager version. Flash 2.5.0.5 and you'll see the same effect.
2) Looking into this now.
3) That's good to hear! Thank you for testing this! This, coincidentally, is primarily how I use CWM as RM has not been stable/consistent for me in ages.
lllboredlll said:
ok
imo if it dont work via rom manager its kind of a deal breaker for me... alot of my users want to use it as well as be able to flashover without having major issues
Click to expand...
Click to collapse
I hear what you're saying.
To get the hooks in place, install 3.0.0.5 first via ROM manager, then go into hboot and install this 3.0.0.6. ROM Manager still thinks you have 3005 and backup/etc. works.
I don't mean this to be production quality, but it should help bridge the gap until koush gets a new version out.

shoman24v said:
Flashed fine here. In the process of making a back up.
I'm diggin the power-off feature.
I only use RM to DL roms, flashing within RM only breaks ****.
Backup sucessfully made.
Click to expand...
Click to collapse
Thank you for testing this! I've updating the OP with notes from both you and bored. And made the disclaimer larger with more ***

No problem. RM still shows 3.0.0.5, but that's not a big deal. I still see the latest nightlies available from RM.
And, like I said, I never flash within RM.
Nor do I recommend that.

tdiman said:
EDIT 2/26/11: This information, as hoped, has been deprecated by the release of CWM 3.0.0.7. You should use that one, because CUViper and koush found more bugs re: the communication between ROM Manager and CWM, as well as the fixes noted below.
Click to expand...
Click to collapse
Just in case someone comes along late to the party, please note the above information added to the OP.

Is it true that v2.5.x.x nandroid backups will not restore under v3.0.x.x clockwork recovery?
Sent from my ADR6300 using XDA App

jdmba said:
Is it true that v2.5.x.x nandroid backups will not restore under v3.0.x.x clockwork recovery?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
no. thats not correct - i have restored a bunch without issues.

I updated to 3.0.0.5 a few weeks ago when it came out. All seems to work fine for me except I can't restore to a previous version to flash other Roms (well at least from Rom Manager). Many of the other Roms that are out right now are not Edify.
Sorry if this is the wrong thread to post this in.
I've googled changing the Roms to edify myself, but I'm kind of lazy and switching recoveries seemed like it would be the easier route.

I think koush has been trying to gently encourage app developers for months to change over.
If you search this forum you'll find older versions of cwm.

The version number is reporting fine for me..... and i Love the new look of the recovery. I'm missing the fast scrolling from the previous builds, other then that I love it

Anyone notice 3007 disappeared from ROM manager for the DINC, I mean as the newest version that is. It is still in the experimental recoveries.

thelunchboxosu said:
Anyone notice 3007 disappeared from ROM manager for the DINC, I mean as the newest version that is. It is still in the experimental recoveries.
Click to expand...
Click to collapse
3008 is in there now also. Fast scrolling is back. I don't know if the glitch with some slcds is fixed.

[Q] Nandroid backup

Hi all
Is Nandroid backing up all the apps I've got at that moment? Or it just saves system files?
Like a complete and exact "photo" or are there things that I should do on my own if I mean to recover exactly as it was...
I assume that no wipe is necessary...
Thanks!

What's the truth about Nandroid backup?!
i guess there's no need to open a new topic, because i got kinda the same question
before you guys start to redirect me to the "search" function, i want to assure you that i have been using it, but i have found myself in a very strange situation, one question, two different answers... and because i'm new to the whole root stuff, i want to learn everything correctly before starting to make modifications to my phone
The question is: Nandroid backup, does it also back up the kernel or not?
I mean, if i root and install a custom rom that also comes with a custom kernel, will i be able to use my previous Nandroid backup to restore my phone to the old rom & kernel?
Searching the forums, i have found 2 totally different answers!
Answer 1: Nandroid does not backup the kernel: http://forum.xda-developers.com/showthread.php?t=806340
Answer 2: Nandroid does backup the kernel: http://forum.xda-developers.com/showthread.php?t=844352
So, please make me and all of us root noobs understand once and for all, does it backup the kernel or not?, will we be able to restore from a custom rom+kernel in case we need to?

and does it backup apps?

OK...As I understand it....
What does Nandroid Backup?
The ROM Itself..Obviously.
All your system settings, emails, SMSes, etc
All the Apps you have installed, so no need for TB
The Kernel you have installed (though there is controversy about this, and to be honest, I have never restored a nandroid backup when I had a different kernel already installed...however it really doesn't matter since kernels are easy to flash)
What does Nandroid NOT backup - This is VERY IMPORTANT
The modem (not a big deal)
The File System setting (A BIG DEAL)
This I think is where the confusion arises concerning the kernel being included in the nandroid backup. For many people the kernel is all about the lagfix. If you have installed a lagfix on your phone via the kernel, say changing the file system to Ext4, and then flash a Nandroid backup that includes a stock kernel or other kernel that does NOT support Ext4, you are in for a world of hurt...and in this case hurt means endless bootloops.
The way you avoid this is, if you need to flash a Nandroid with a kernel that does not support your lagfix...go into recovery, disable whatever lagfix, tell it when it asks that you wish to REBOOT INTO RECOVERY after the change....then flash the nandroid you wish.
This is why it is very important to keep regular nandroid backups, and to wait and see if a ROM/Kernel are stable for you before applying lagfixes or other tweaks.

So, let me see if i got this right, Nandroid does backup up my current kernel along with my rom, but if i apply any changes (lagfix) to my kernel afterwards or change it with a custom one with lagfix, nandroid won't be able to restore it anymore...
so the whole problem here is that nandroid is not able to backup / restore The File System setting, this being the rfs / ext4 transition
If this is the case, it seems that the Nandroid type backup is not as powerful as i thought, you can't really change from one rom to another in just a few clicks, but then again i guess that all the customs roms already come with some type of lagfix and you can make a nandroid restore between them, the problem would be when you want to revert back to a stock kernel, then you'll have to disable the lagfixes or simply flash a stock kernel and then restore the stock nandroid backup
so, i got this right guys?

maranello69 said:
So, let me see if i got this right, Nandroid does backup up my current kernel along with my rom, but if i apply any changes (lagfix) to my kernel afterwards or change it with a custom one with lagfix, nandroid won't be able to restore it anymore...
so the whole problem here is that nandroid is not able to backup / restore The File System setting, this being the rfs / ext4 transition
If this is the case, it seems that the Nandroid type backup is not as powerful as i thought, you can't really change from one rom to another in just a few clicks, but then again i guess that all the customs roms already come with some type of lagfix and you can make a nandroid restore between them, the problem would be when you want to revert back to a stock kernel, then you'll have to disable the lagfixes or simply flash a stock kernel and then restore the stock nandroid backup
so, i got this right guys?
Click to expand...
Click to collapse
Yes as I understand it.
You see Nandroid can't convert your file system or change anything, all it can do is flash a disc image onto your phone. If that image can work with your file system, you are golden. If not, it is like flashing a Mac OS image onto a Windows machine....nothing will work right.
However the good news is that most custom kernels support Ext4...so really the only problem comes when you try to flash back to a stock image...or vice versa.

got it then, thanks for your answers
and, if i still got your attention, maybe one more question
i just downloaded a stock firmware from samfirmwares.com, and all i got is a .tar file, can i use it somehow to flash just the kernel from it or i have to flash the whole firmware?
if i flash the whole firmware, will it also change my PHONE and CSC?, because the .tar file must be put just in the PDA section in odin

maranello69 said:
got it then, thanks for your answers
and, if i still got your attention, maybe one more question
i just downloaded a stock firmware from samfirmwares.com, and all i got is a .tar file, can i use it somehow to flash just the kernel from it or i have to flash the whole firmware?
if i flash the whole firmware, will it also change my PHONE and CSC?, because the .tar file must be put just in the PDA section in odin
Click to expand...
Click to collapse
Yes, it will flash the PDA, csc, modem and kernel...the whole shooting match. The single file firmwares are designed like that to avoid mismatches and issues. Once you flash it, flash a kernel that supports cwm (I suggest speedmod or something by CHAINFIRE) via odin, then flash a new csc and modem if you wish from recovery.
Remember that installing a new csc will do a factory reset so do it before reinstalling apps.
Sent from my GT-I9000 using XDA Premium App

great stuff man
finally i got enough info and i can start my root & flash procedure, guess i'll also learn a few other tricks along the way, this community is definetly the place to be if you want to learn how to "really use" your device
the whole info about the issues with the Nandroid type backup should be integrated in one of those massive info topics, so the root noobs like me know what they're dealing with

maranello69 said:
great stuff man
finally i got enough info and i can start my root & flash procedure, guess i'll also learn a few other tricks along the way, this community is definetly the place to be if you want to learn how to "really use" your device
the whole info about the issues with the Nandroid type backup should be integrated in one of those massive info topics, so the root noobs like me know what they're dealing with
Click to expand...
Click to collapse
Good luck
Sent from my GT-I9000 using XDA Premium App

Hey guys i actually used the search button (yay) and this is definitely the most informative one regarding the topic.
However i still have one more question: does it backup files and folders as well? Ie. my Nexus S storage is mainly used up by my videos and music (about 7-10GB) which are in their own folders and not tied to any apps in particular. Hence if it does include those i wouldn't have enough storage space to create a nandroid backup am i right?
Edit: thanks to the search button i didn't realise that i posted on a Galaxy S forum please forgive me, the question should still be relevant to the topic though

frenccw said:
Hey guys i actually used the search button (yay) and this is definitely the most informative one regarding the topic.
However i still have one more question: does it backup files and folders as well? Ie. my Nexus S storage is mainly used up by my videos and music (about 7-10GB) which are in their own folders and not tied to any apps in particular. Hence if it does include those i wouldn't have enough storage space to create a nandroid backup am i right?
Click to expand...
Click to collapse
As I understand it, it does save folders and files, so yes if you have large data folders on your internal SD it will make GIGANTIC nandroid backups. You may want to store such files one your external SD.
I know that there is a version of CWM that does not backup /data/media in Nandroid on the Galaxy Tab 10.1...perhaps there is something similar that I don't know about for Galaxy phones. Does anyone know?

[Q] Help with stock Milestone 2.2.1 from Germany

Hi everyone,
I know this will make me sound like a complete noob but it doesnt matter. Any help or any pointing in the right direction would be greatly appreciated.
I have a stock motorola milestone 2.2.1. I hate it and have read how stable some of the roms are and I would love to experiment with them. However, never having a windows phone or an HTC before I have no idea how to do this with minimizing the risk.
So I have rooted my phone with universalandroot and have installed rom manager and titanium backup. Unfortunately, I read that rom manager wont work with the Milestone.
All of the threads on boot recovery and other methods seem to differentiate from one another. Is there a safeR method. I know no method is safe. What programs do I need to install on my computer and or my phone for this to work?
I know this a lot and I truly appreciate any help and support from this forum.
Thanks

Tompaine said:
Hi everyone,
I know this will make me sound like a complete noob but it doesnt matter. Any help or any pointing in the right direction would be greatly appreciated.
I have a stock motorola milestone 2.2.1. I hate it and have read how stable some of the roms are and I would love to experiment with them. However, never having a windows phone or an HTC before I have no idea how to do this with minimizing the risk.
So I have rooted my phone with universalandroot and have installed rom manager and titanium backup. Unfortunately, I read that rom manager wont work with the Milestone.
All of the threads on boot recovery and other methods seem to differentiate from one another. Is there a safeR method. I know no method is safe. What programs do I need to install on my computer and or my phone for this to work?
I know this a lot and I truly appreciate any help and support from this forum.
Thanks
Click to expand...
Click to collapse
First of all, ROM Manager does not work with the milestone. So please remove it and dont ever install Clockworkmod recovery on the milestone.
Second, What ROM do you want to install?
You need Androidiani Openrecovery for all your flashing needs of customs ROMS. You will need rsdlite to flash sbf files and offcourse the Moto usb drivers. Check the sticky threads in the development section. There are many tutorials.

This is easily one of the best ways to get everything done in the way of flashing a custom ROM.
http://forum.xda-developers.com/showthread.php?t=983516
Depending on which ROM you want to install, it will determine what you need to download.
After rooting the phone, you will want to flash a vulnerable recovery sbf via RSD Lite, as shown in that thread the VR you should use will depend on your bootloader version. If you are running 90.78, then you can flash this VR: http://android.doshaska.net/rootable
After that happens, you can create a backup of all of your apps using TitaniumBackup.
Once you do that you want to place OpenRecovery(AOR) on your SD Card. Follow the steps from the first link I posted to get that on. You will want to place the custom ROM that you want into OpenRecovery/updates. If you are planning on using CM7, you will also need to download google apps from the CM7 thread here.
Once that is on, you will want to boot into recovery(power+x, see the Moto M logo, then release and push camera button+volume up), apply update.zip.
From there you want to select the Nandroid menu with the d-pad. Create a nandroid backup of what you want.
Now is the crucial step. You need to wipe the caches and ALL data. Choose wipe dalvik cache, wipe cache partition and wipe data/factory reset.
Now is time to apply your custom ROM!
It is recommended to create a nandroid backup everytime you flash a custom ROM, in case of anything going wrong.
Navigate to apply update in AOR, select the ROM that you want, select yes. Once it is done installing, wipe the caches and data AGAIN.
If you are installing the google apps, you will want to wipe the caches, flash the google apps, then wipe the caches again.
You will probably have to apply the baseband for your carrier, so you will need to navigate to change baseband, and apply the baseband for your carrier.
If you followed those steps, you should have a brand spanking new custom ROM on your phone.
Hope this helps.

@skadude66
I just really want to thank you so much for helping me with that. Your tips and the link to the guide explained step by step what I had to do.
Right now I am running miui gingerbread on my phone and it runs and looks great. Thanks.

Tompaine said:
@skadude66
I just really want to thank you so much for helping me with that. Your tips and the link to the guide explained step by step what I had to do.
Right now I am running miui gingerbread on my phone and it runs and looks great. Thanks.
Click to expand...
Click to collapse
Glad to hear!
Sent from my Milestone using XDA Premium App

[Q] Help with root and custom ROM.

Hello guys,
I've been looking around hier for a while, and I spotted a Custom ROM that I'd like to try, it's this one: http://forum.xda-developers.com/showthread.php?t=1424260
I've never rooted my phone before so I don't have experience with it.
I found a couple of threads that can help me but, I don't know in wich order I have to follow them.
First of all, I'd like to make a complete back-up of my current ROM, so in case something goes wrong, I can restore it. How do I do this? I read something about ClockWorkMod and a nandroid back-up, can somebody clear this out?
I have an unrooted HTC Incredible S with S-ON. So first, I think that I have to get S-OFF? I found a tutorial with the Revolutionary tool, but it doesn't support my HBoot, so I think that's not an option?
So then, I found this tutorial: http://forum.xda-developers.com/showthread.php?t=1337105
The tutorial is easy to follow, but can I create a full back-up before I start the tutorial?
And to get S-OFF, do I need a rooted device?
I hope somebody can help me. If you need more information, just ask.
Here is some information about my device:
- Android 2.3.5
- HTC Sense 3.0
- S-ON
- Not rooted
- HBoot 2.00.0000
- No SIM-lock
If more information is needed, please ask.

Unfortunately having your current h-boot the method available to you to root and install custom ROMs does not let you back up your phone prior to flashing. As the method used is flashing a new ROM that allows root access to your phone. Prior H-boots (1.13.0000) allowed you to root your phone without flashing a custom ROM thus unlocking boot loader to be flashed CWM as a custom recovery and allowing you to create a nandroid backup of your current state before flashing a new rom. However[/] the process you are going to need to complete might contain a back-up function included in the flashing process, I don't know for sure as I flashed from 1.13.0000, but it doesn't really matter as your going to have to complete the process anyways. I say just go for it and follow the instructions to the "T". If you follow everything properly and take your time you shouldn't encounter any problems.

In the tutorial I posted, step 10 is
10. Using volume up/down and power to select, go down to Backup/Restore. Select it, then hit Backup. ClockWorkMod will backup your stock ROM in case there are any dramas and you want to go back to it.
Click to expand...
Click to collapse
Will this create a complete back-up? So when I restore it, will everything be back the way it is right now?

MrSenne said:
In the tutorial I posted, step 10 is
Will this create a complete back-up? So when I restore it, will everything be back the way it is right now?
Click to expand...
Click to collapse
Exactly. Stay safe.

So if I just follow that tutorial, I will have a Custom ROM with root? And do I still have to get S-OFF?

You don't need to go S-OFF to flash a custom rom. There is actually no need whatsoever to go S-OFF, unless you want to go and flashing other radios. But the lastest sense 3.0 and android 2.3.5 update included the lastest radio, so keep S-ON. Better for warranty.
First go to htcdev.com and follow the instructions to unlock bootloader. BE AWARE THAT THIS WILL WIPE YOUR PHONE TO FACTORY DEFAULTS for security reasons, sdcard remains untouched.
After bootloader unlocked you can flash the clockwork recovery (you're still S-ON). Once you flashed that you can go into recovery with volumebutton down and power on. Take a backup with clockwork (=nandroid = full image of the phone in its current state) of your original rom and start flashing custom ones.
They're is probably a time where you gonna think you bricked your phone, I have. But I always got through it by searching the forum. Always, in any circomstance, manually push the boot.img of the associated rom from a PC to your phone. So never flash a ROM from your sdcard if you don't have a PC in hand. Otherwise it will probably not boot or get hardware not working (not broken in anyway, just not properly loaded).
Before changing roms, I always do the ARHD wipe script. Just to be sure every trace of the previous rom is gone. There are multiple partitions on your phone (system, data, boot). It wipes all of them to start clean.
The ROMs you are going to flash are rooted by default.
So now, of you go and be a ICS beta tester

Thanks fot the explenation.
But, because I can't root my phone because it's HBoot 2.00.0000; I can't make a back-up of it? Not even with Titanium Back-up.
Is there any way I can back-up my app's? So I don't lose all the saved data in the app's?

MrSenne said:
Thanks fot the explenation.
But, because I can't root my phone because it's HBoot 2.00.0000; I can't make a back-up of it? Not even with Titanium Back-up.
Is there any way I can back-up my app's? So I don't lose all the saved data in the app's?
Click to expand...
Click to collapse
As far as I know the answer is "no".
You need clockwork for a nandroidbackup, you need bootloader unlocked for clockwork, unlocking bootloader wipes your phone.
I accidently wipe mine with the unlocking of the bootloader. It seems harder than it is to start over. Just link contacts and calendar with gmail, backup sms on sdcard in messaging. That's all you need. Starting over is good to get the crappy apps gone

Hmm, okay, then I'll have to do it without making a back-up.
And is there an easy way to switch between ROM's? Without using a computer.

MrSenne said:
And is there an easy way to switch between ROM's? Without using a computer.
Click to expand...
Click to collapse
It is very easy to change roms. They are stored in zip-format on your sdcard which you can browse to with clockwork. Also the nandroidbackups are stored on your sdcard and can also be chosen with clockwork.
Experience tells me that you still need to flash the boot.img of the rom manually after you flashed the rom (something to do with clockwork not able to write in boot partition while in recovery-mode, you have to be in fastboot-mode). Flashing the boot.img litterly takes 2 secs to upload, done, and reboot.
So it is no big deal to swich:
- boot in recovery
- browse to the desired rom/backup
- start and wait 5 mins
- boot in fastboot
- connect to pc and flash boot.img
- wait 2 secs and reboot
Do not flash when you need the phone and there is no pc around. If it goes wrong, you need your usb pc to fix things.

I heard something about Rommanager, can I use this and what does it do excactly?

MrSenne said:
I heard something about Rommanager, can I use this and what does it do excactly?
Click to expand...
Click to collapse
ROM Manager is an app that works with ClockworkMod recovery to keep it up to date and allows you to make and manage CWM nandroid backups and manage partitions on your SD card. The paid version also allows you to download custom ROMs and flash them.
It requires root access in order to run.

But it's not a necessary application?

MrSenne said:
But it's not a necessary application?
Click to expand...
Click to collapse
No, not really.

Ok, propably I'll try it this evening.

Thanks for everything who helped me, I followed the tutorial and everything is working fine.