Database Info

[Q] NAND Unlock (How to?) / BusyBox Help

Morning guys,
Sorry if this has been asked/answered in a previous thread (couldn't find one specific to the EVO Shift)
I have already perm-rooted my Shift (S-Off) and I was looking through some apps for root only and one in particular (Font Changer (root)) explicitly requires "*FULL ROOT* (aka NAND unlocked or S-OFF) and *BUSYBOX*"
Ok, so I believe I have full root, unsure about the NAND though
And I have been having problems with BusyBox getting installed (still using stock Froyo 2.2 ROM)
Thanks

doratheconquistadora said:
Morning guys,
Sorry if this has been asked/answered in a previous thread (couldn't find one specific to the EVO Shift)
I have already perm-rooted my Shift (S-Off) and I was looking through some apps for root only and one in particular (Font Changer (root)) explicitly requires "*FULL ROOT* (aka NAND unlocked or S-OFF) and *BUSYBOX*"
Ok, so I believe I have full root, unsure about the NAND though
And I have been having problems with BusyBox getting installed (still using stock Froyo 2.2 ROM)
Thanks
Click to expand...
Click to collapse
boot into hboot (where you do recovery) and look at the top line, it should say s-off if your nand is unlocked (which was done when you flashed the engineering spl).
where are you getting busybox from?

doratheconquistadora said:
Morning guys,
Sorry if this has been asked/answered in a previous thread (couldn't find one specific to the EVO Shift)
I have already perm-rooted my Shift (S-Off) and I was looking through some apps for root only and one in particular (Font Changer (root)) explicitly requires "*FULL ROOT* (aka NAND unlocked or S-OFF) and *BUSYBOX*"
Ok, so I believe I have full root, unsure about the NAND though
And I have been having problems with BusyBox getting installed (still using stock Froyo 2.2 ROM)
Thanks
Click to expand...
Click to collapse
If you're s-off, you're good to go.
For busybox, download titanium backup and select Problems? That'll take care of it.
If all else fails, use your recovery! Make a nandroid, format all partitions and wipe dalvik cache, then flash preludedrews stock base.
Sent from my PG06100 using XDA App

I've tried BusyBox from both the Market and the one under Problems? with Titanium Backup
Ok, so at least I know that I'm NAND unlocked too
How exactly do I do this?
"Make a nandroid, format all partitions and wipe dalvik cache, then flash preludedrews stock base"
The problem is that no matter how long I wait, BusyBox is stuck at the Please Wait screen "Please wait while we locate BusyBox and gather system data..."

doratheconquistadora said:
I've tried BusyBox from both the Market and the one under Problems? with Titanium Backup
Ok, so at least I know that I'm NAND unlocked too
How exactly do I do this?
"Make a nandroid, format all partitions and wipe dalvik cache, then flash preludedrews stock base"
The problem is that no matter how long I wait, BusyBox is stuck at the Please Wait screen "Please wait while we locate BusyBox and gather system data..."
Click to expand...
Click to collapse
I assume you flashed a recovery image, yes?
Boot the phone up holding vol. down and power. You should be in the S-Off Engineering SPL (bootloader)
Follow the instructions for recovery, which I believe is vol. down again, then while in recovery select Backup/Restore. Create a backup.
Do a data and cache wipe via the main menu in recovery, toggle down to advanced and wipe dalvik cache.
Then go to Partitions, or Mounts and Storage depending on the recovery. Format /boot /system /data and /cache.
Install zip from sdcard -> select the base rom you downloaded from the android development section.
Sent from my PG06100 using XDA App

Can't Mount Data, Cache or Failed PU

I wanted to start this thread so we can a place where everyone who discovers this issue, comes here and posts on what they did, how they managed to recover from it, and what steps they have taken on preventing this from happening.
I've been lurking around and it seems as if it's the users with the gfree method thats it's only happening too.
I wanna keep track how it happens, as the glacier isn't the only one that suffers from this but it's been happening quite often these past few days. Thanks
Please state how it happen, what rom you flashed and or nandroid backup and if you pulled your battery during a flashing, wiping session.
I can confirm that we're not the only ones that this is happening too. G2 users are also having the same exact problem. There seems to be a really good chance of why this is happening because of different emmc chips and or drivers, i'll be looking through irc logs and put out a summary here for all.
And also, check this out. I know our devices varies from the G2 quite a bit, but then again we're using the same rooting method and exploit so it makes sense to check some stuff from there. http://forum.xda-developers.com/showthread.php?p=13234526

I am sorry if I sound like a nood , but I am a noob:© . I used the gfree mathed to root my phone, didn't run into the problem you are discrubing. Mybe I didn't quite get it.
Sent from my HTC Glacier using XDA Premium App

ummm yea.... happened to me today and after trying basically everything (nandroid restore, flash rom via zip, flash official rom via bootloader etc.) nothing worked
It happened when i was using Virtous Fusion and decided to flash back my Cyanogenmod 7 backup. I has the latest clockworkmod 3.0.2.4, Cleared data / cache and ran the restore... after it was done, i rebooted and noticed that it would not go past the Mytouch splash screen... went back to recovery via the vol down + power combo only to be greeted with...
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Nandroid backups dont flash, zip roms flash (or it seems) but doesnt boot, i get errors when i try to wipe, flashing official rom via bootloader gives me the dreaded FAIL-PU after most steps, so yea... im boned lol
Apparently there is a chance to restore if u got the engineering bootloader but i did not at the time. I did root via gfree since the visionary method refused to gain s-off

I wonder if it has something to do with restoring after clearing data/cache instead of directly restoring... I've never cleared those before a restore and I have never had an issue. let's get some other people in here to test that theory.

kimbernator said:
I wonder if it has something to do with restoring after clearing data/cache instead of directly restoring... I've never cleared those before a restore and I have never had an issue. let's get some other people in here to test that theory.
Click to expand...
Click to collapse
You should be clearing data and cache before restores. There are a lot of things in /data that do not carry over well when changing ROMs. I wonder if it's something to do with ClockworkMod 3.x recoveries.

here you go this is my experience:
http://forum.xda-developers.com/showpost.php?p=13709837&postcount=22

All the users who had this trouble Were rooted with gfree. Any users with the first s-off method?
_ice_ said:
here you go this is my experience:
http://forum.xda-developers.com/showpost.php?p=13709837&postcount=22
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App

mike21pr said:
It happened when i was using Virtous Fusion and decided to flash back my Cyanogenmod 7 backup. I has the latest clockworkmod 3.0.2.4, Cleared data / cache and ran the restore...
Click to expand...
Click to collapse
You know you should do a factory reset via the recovery image prior to flashing any new ROM. ESP when coming from a 2.2 ROM to a 2.3 ROM.
I wonder if that is what is causing the problem. The Clockwork ROM Manager doesn't wipe everything the "factory reset" in the recovery image itself.

neidlinger said:
You know you should do a factory reset via the recovery image prior to flashing any new ROM. ESP when coming from a 2.2 ROM to a 2.3 ROM.
I wonder if that is what is causing the problem. The Clockwork ROM Manager doesn't wipe everything the "factory reset" in the recovery image itself.
Click to expand...
Click to collapse
You don't mean do the "factory reset" on the HBOOT screen do you?
So.. going from say a 2.2.1 stock to 2.3.3, do... (through clockworkmod recovery screen NOT ROM MANAGER APP)
1. wipe data/factory reset
2. wipe cache partition
3. wipe dalvik (optional?)

If you don't use Rom mamaher to load your Roms , would you run in to the same problem.?
Sent from my HTC Glacier using XDA Premium App

h22aboi said:
You don't mean do the "factory reset" on the HBOOT screen do you?
So.. going from say a 2.2.1 stock to 2.3.3, do... (through clockworkmod recovery screen NOT ROM MANAGER APP)
1. wipe data/factory reset
2. wipe cache partition
3. wipe dalvik (optional?)
Click to expand...
Click to collapse
Wipe data factory reset is broken in cwm 3.0.2.4 it hangs when it comes to /data or /cache especially if you have a cooked rom flashed before from an amateur developer.
I noticed that /data or /cache sometimes do not mount properly thus leaving behind corrupted files.
So my advice is to use the advanced format menu in cwm.
1. Wipe dalvik
2.mount /cache, wipe /cache
3. Wait for it, then mount /system, wipe /system
4. mount /data and wipe /data <--- last
Also because some roms come w autowipe feature sometimes when it tries to wipe an already wiped partitions then sectors get corrupted. So if the rom has auto wipe feature built in. You do not need to wipe /system or /data
Sent from my HTC Glacier using XDA App

jdkoren said:
You should be clearing data and cache before restores. There are a lot of things in /data that do not carry over well when changing ROMs. I wonder if it's something to do with ClockworkMod 3.x recoveries.
Click to expand...
Click to collapse
Restoring clears those partitions by itself. I've always been taught that it's only necessary to clear those partitions when you install a new rom, but restoring does it all by itself. I've restored probably more than 15 times without any clearing and it works fine.
Also, I didn't use gfree, and I might not if people get these errors when they do.

Yeah, this is my third mytouch, and this is the only one I used gfree on. I remember with my second one I didn't use the gfree method and I flashed and did everything without any of these risks. Im stilling leaning towards the gfree method being the culprit for the recovery errors.
kimbernator said:
Restoring clears those partitions by itself. I've always been taught that it's only necessary to clear those partitions when you install a new rom, but restoring does it all by itself. I've restored probably more than 15 times without any clearing and it works fine.
Also, I didn't use gfree, and I might not if people get these errors when they do.
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App

xdviper said:
Yeah, this is my third mytouch, and this is the only one I used gfree on. I remember with my second one I didn't use the gfree method and I flashed and did everything without any of these risks. Im stilling leaning towards the gfree method being the culprit for the recovery errors.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
yes sir, that could be another factor. gfree is mainly for CID unlock and "true root" but thing is true root isn't required... every other rom flashes -.- gfree also alters your dev block partition which can cause issues.

This thing has me a little worried.
I used the gfree method from the CM Wiki for the Glacier. I have s-off and hboot .85, but I am a bit more hestitant now to flash different roms seeing as how many people are having problems. However, I don't like Rom Manager and never use it. I always go through CWR to flash so is that better? And I am on 3.0.0.6.

FYI, according to trueblue_drew he says to do this as far as wiping your stuff on flashing one of his roms...
This is how you should wipe:
Main Recovery Menu:
1. Wipe data / factory reset
2. wipe cache partition
Advanced Recovery Menu:
3. Wipe Dalvik Cache
Mounts and Storage Recovery Menu:
4. Format System
Sent from my HTC Glacier using XDA

I got the fail PU error a week ago. I was on an miui rom and was restoring a backup I had of cm7. When I rebooted after the restore the phone would not load past the splash screen. I booted back into recovery and noticed the E: Can't mount/cache errors. I tried to flash a new rom but when I would reboot it would not go past the splash screen still. That's when I looked up the problem. I then tried to restore with the PD15IMG, but got the fail PU errors. I then read that you need the part7backup on the sd card if you are going to use the PD15IMG. So I did and stilll got the fail PU errors, but this time it was stuck loading the radio. I pulled the battery. Would not even turn on after that.
I too had rooted with the gfree method and had the engineering bootloader.
I called T-mobile to replace the phone since it wouldn't even turn on anymore. Took 2 hours to get them to send a replacement with free shipping. They accidentally sent me 2. Two separate boxes, same shipping number. At least now I have a backup. I already rooted one. I did not use the gfree method this time.

Since it seems to be a gfree problem, should I go to stock and re-root the phone using another method??

tilt4life2 said:
Since it seems to be a gfree problem, should I go to stock and re-root the phone using another method??
Click to expand...
Click to collapse
Well, that's what I'm probably going to end up doing as well. This is my third replacement and the first method to root didn't stick, so I ended up rooting with gfree. I am going to unroot and try rooting with the first method which is here http://theunlockr.com/2010/12/10/how-to-gain-permanent-root-and-s-off-on-the-t-mobile-mytouch-4g-htc-glacier/ but the thing is, if it doesn't stick, we're back at gfree.
Anyone know any G2 users that have/had this problem? We're using the same rooting method so there should be a couple people who faced this.

Alright well I've been reading logs from G2_Root channel from April 26th and so on, and it looks like the G2 has two different types of the emmc chip. Gfree powers off this chip and then initializes the chip again in order to get around the write protection. I remember before we had root access on the G2 (before I traded for a mytouch) I would lurk around the irc channel and read progress. I remember having to get the chip to power on in order to get around the write protection.
Now it looks like while the phone is being used, or booting up and or trying tto read or write from emmc the chip suddenly dies. This is what causes us to get force closes, freezes and not being able to get past the splash screen and also explains the recovery not being able to mount partitions.
We're going to need people to join in the G2 channel preferably ones who still have their defective phones to get some data off it.
Again, this is a very vague summary of what I've been able to read off the irc logs.
Why the G2? Because we're using the same gfree method to root our phones and with our phones dying it makes sense.
I think, they have already ruled out recovery and the Eng hboot to be culprit but this is just too early in the game to determine.
Here's a thread from the G2 side, if anyone still has this problem with their cache not being to mount please check out post #13.
I'll look.around more and see what I find from the G2 side.
http://forum.xda-developers.com/showthread.php?t=1039504
Sent from my HTC Glacier using XDA App

[Q] Switch from 4EXT to CWM ? / Flashing boot.img ? (CM10-alpha)

Hi XDA
My device before the procedure : HTC Desire S, unbranded, Bootloader locked,
HBoot 2.00.0002, S-ON, ICS stock rom via HTC RUU tool
I unlocked the bootloader via htcdev.com.
After hours of reading and testing "everything" I found here on xda (great stuff!!),
I finally managed to have a running CM10-alpha.
(http://forum.xda-developers.com/showthread.php?t=1776256 / Version 2012-09-17)
As I am new to this flashing stuff, I first tried to follow the flashing guide
on the CM-website. Was not workable because "Revolutionary" can not be used on hboot 2...
So I continued with flashing CWM-recovery and after a wipe (factory/reset/cache/dalvik),
I flashed CM10.zip and gapps.zip.
It went through without any errors, unfortunately, the device did not boot afterwards.
I found this guide :
http://forum.xda-developers.com/showthread.php?t=1525100 (CustomROM with 4EXT-recovery)
It indicates flashing "boot.img" (from the CM10 zip-file) as a last step.
Probably the most important step for this HTC device ?!
The Desire S booted CM10 without any further problems and is running since.
(I did not flash GApps.zip, just downloaded Maps and Youtube.)
I have 3 questions :
1. Is it possible to update to a newer version of 4EXT-recovery without losing
the CM10-installation ?
(e.g. 4EXT-Touch : http://forum.xda-developers.com/showthread.php?t=1377745)
2. Is it possible to switch from 4EXT to CWM-recovery without losing
the CM10-installation ? I would like to have CWM because I could then use the ROMManager App.
(e.g. http://forum.xda-developers.com/showthread.php?t=1484753)
3. If I would stick with the current 4EXT-recovery,
do I always have to flash "boot.img" as the last step before booting up the device ?
(e.g. after the next CM10-alpha release)
"fastboot flash boot boot.img"
Click to expand...
Click to collapse
Thanks so much !
CM10 is great, so much faster than HTC-stock rom ICS (with Sense 3.6) !!
CU

1) yes
2)yep
3)si
Edit: you only have to flash the boot.img when the kernel changes from cm10 to fallout yes.
Updating cm10 no, if the dev didn't change the kernel.
After a full wipe (in 4ext format everything exept SD-card) you also have to use fastboot. Because that wipes the boot.img

Thanks !
Just to recap, I can flash CWM-recovery and then do a normal bootup (with my existing CM10 installation). No further actions required !?
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.

FrolicFrog said:
Thanks !
Just to recap, I can flash CWM-recovery and then do a normal bootup (with my existing CM10 installation). No further actions required !?
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
Click to expand...
Click to collapse
Changing recovery will not touch anything else on your device. But there were some issues reported with CWM on some ROMs.
I think one of them is a lack of /system/lib partition support, which is important if you go from a ROM that has such to a ROM without one (it will end with two conflicting /system/lib directories and the device will not boot.
Also I am not sure that CWM wipes the .android-secure directory on the SDcard which can cause issues if going from AOSP to Sense ROM

For some reason I never changed from cwm to 4ext whilst I owned a ds but I can confirm it does wipe .android-secure on the sd card

pughie said:
For some reason I never changed from cwm to 4ext whilst I owned a ds but I can confirm it does wipe .android-secure on the sd card
Click to expand...
Click to collapse
I have used it about an year ago so it is definitely improved. But there was an user with Bluetooth issues after flashing my kernel and changing the recovery solved it. Also 4EXT has a lot of minor but very useful settings over CWM. Anyway the OP can try both and stick with the one he likes more
Btw Rom Manager can be used to check for updates and ROM downloads with 4EXT if you choose "manual flash override" from the menu
Sent from my HTC Desire S

amidabuddha said:
Btw Rom Manager can be used to check for updates and ROM downloads with 4EXT if you choose "manual flash override" from the menu
Click to expand...
Click to collapse
Ah, will check on this one. Thanks !

FrolicFrog said:
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
Click to expand...
Click to collapse
Nk111 uploaded a screenshot today, that shows kernel v3.0.16
When upgrading cm10 wiping cache & dalvic cache should be enough. If you get any problems, apps fc or something like that, do a full wipe(I use format all partitions except SD card in 4ext, after that don't forget to flash the kernel with fastboot).
Btw wipe and format is the same.

Bug in CM10 Alpha by nk11
Hello XDA,
Sorry if this question is in the wrong thread.
It is regarding the cm10 alpha port by nk111.
I got it working, save one major bug, the speaker does not produce any sound output whatsoever:
This applies to ringtones, alarm tones and music.
The sound is perfectly audible through a pair of earphones.
I followed the steps in the official thread to delete the file /system/lib/hw/audio_policy.msm7x30.so and reboot
but this only aggravates the issue by disabling all audio outputs!!!
I am running clockwork mod v5 with HTC bootlocker unlocked, S-ON.
Any help would be greatly appreciated.

c.m.b said:
Nk111 uploaded a screenshot today, that shows kernel v3.0.16
When upgrading cm10 wiping cache & dalvic cache should be enough. If you get any problems, apps fc or something like that, do a full wipe(I use format all partitions except SD card in 4ext, after that don't forget to flash the kernel with fastboot).
Btw wipe and format is the same.
Click to expand...
Click to collapse
I saw the screenshot of kernel version 3, too. And was quite excited
Thanks for the hint with wiping only cache&dalvik.

DEV help, or experienced tweakers (MIUI, CleanROM)

Trying various ROMs before i decide on one to get settled in to.
1. MIUI 2012.09.14
- flashed ok, rebooted, stuck on startup animation doesnt boot.
(downloading 2012.09.29)
2. CleanROM
- flashed ok, rebooted ok, error; "com.android.phone has stopped working" before i get past lock screen.
This happens another 2 - 4 times while im trying to get thru phone setup.
Before eventually it boots back to startup animation, and repeats the process.
3. CNA
- flashed ok, rebooted ok, loaded semi ok before multiple errors;
Unfortunately phone has stopped.
Messaging has stopped.
System UI has stopped working.
Any ideas? I was kinda keen to see all of of these ROMs operate.

Wobzy said:
Trying various ROMs before i decide on one to get settled in to.
1. MIUI 2012.09.14
- flashed ok, rebooted, stuck on startup animation doesnt boot.
(downloading 2012.09.29)
2. CleanROM
- flashed ok, rebooted ok, error; "com.android.phone has stopped working" before i get past lock screen.
This happens another 2 - 4 times while im trying to get thru phone setup.
Before eventually it boots back to startup animation, and repeats the process.
3. CNA
- flashed ok, rebooted ok, loaded semi ok before multiple errors;
Unfortunately phone has stopped.
Messaging has stopped.
System UI has stopped working.
Any ideas? I was kinda keen to see all of of these ROMs operate.
Click to expand...
Click to collapse
1) you must be on newer hboot and need to flash boot.IMG via fast boot manually.
2) you need to do a factory data reset then reflash.
3) Same as number 2.
Sent from my One X using xda app-developers app

h8rift said:
1) you must be on newer hboot and need to flash boot.IMG via fast boot manually.
2) you need to do a factory data reset then reflash.
3) Same as number 2.
Click to expand...
Click to collapse
Cheers bud, awesome.
The steps only said wipe, and someone had told me factory reset only works on stock ROM?
Incorrect?
And forgive my ignorance, hboot?

Ok heres where im at;
- reset to bootloader
- factory reset
- booted to twrp
- wipe system (not sdcard)
- install (no roms, no backup of stock - sdcard is wiped)
kinda panicked a little.
- mounted as usb
- copied roms from laptop back to sdcard
- install (still no roms)
getting more panicked.
- create partition intending to copy roms over again
- roms mysteriously just appear on sdcard after partition created
- installed cna, had one error of unfortunately system ui has stopped working, but no reoccurence.

Never factory reset or clear storage or any of that in hboot. You were supposed to factory reset in twrp. Factory reset in twrp clears data,cache,dalvik it does not wipe your storage.

All of those must of been dirty flashes ...just USB mount in twrp. And copy a rom over

DvineLord said:
Never factory reset or clear storage or any of that in hboot. You were supposed to factory reset in twrp. Factory reset in twrp clears data,cache,dalvik it does not wipe your storage.
Click to expand...
Click to collapse
****. Thanks.
The partition i created to backup and hold roms was 2gb.
In file manager & when mounted as usb i can see the files i copied over as well as the standard sdcard folders.
But i cant see any evidence of a partition.
Only when i check my available space my total sdcard is now 24gb.
Can u help me understand also how i couldnt see the copied files until i created the partition in recovery?

I did some bootloader wipes and recovery wipes, ended up messing up storage bad. Had to ruu in the end.

DvineLord said:
I did some bootloader wipes and recovery wipes, ended up messing up storage bad. Had to ruu in the end.
Click to expand...
Click to collapse
Ok i searched and downloaded the RUU based on my hboot info;
- RUU Evita UL Telstra WWE 1.89. 841.9 Radio 0.18c.32.09.01 10.9 3a.32.20L release 266699 signed .exe
Just in case i've left anything out or anyone wants to jump in, this is the story;
Brand new stock Telstra HTC One XL (Australia)
Unlocked & rooted, TWRP recovery.
Backed up stock.
Installed a few different ROMs before deciding on one.
Accidentally reset factory from hboot instead of twrp.
Lost stock ROM back up.
Mounted USB & copied custom ROMs back across to sdcard.
Files did not appear on sdcard.
Decided to partition and try again.
On sucessful partition, suddenly all files became visible, despite partition warning "all files will be deleted"
Flashed Viper XL successfully.
SDcard total storage reading as 24gb (32gb stock)
1. if i have done anything to reduce my available storage i want to get it back.
2. id like to go back to stock rom and basically start from scratch with clean stock backup and clean storage.
I found a link to the ATT One X stock rom on the US HTC support site.
I cant find anything similar on the AU site for the One XL.
On the xda thread the link was located on, i read that i have to re-lock my bootloader, thats fine theres a tutoriall, but i need to find the stock rom.
That tutorial however didnt mention anything about RUU.
Will ruu enable me to do this internally?
Thanks in advance.

All sorted, RUU is at 15% thx for the help.

There is a 1.89 being hosted in the football ruu collection and other places if you havent found it already, dont run the at&t 2.20 ruu.

Just rooted my phone

Do I have to factory reset in recovery and does factory reset result in Bootloop,
Do I have to Superwipe.
Or do this individually:
Format/wipe data
Wipe cache
Wipe dalvik cache in advance(menu)
Format SD ext, system, boot, in mounts and storage.

What do you wan't to do with the phone, factory reset from menu will get you to bootloop for sure, doing it from recovery...... it's 50/50. But why do you want to do this?
If you want to change the rom, then just follow the instructions for it, so please do tell, what is your goal.

I just rooted my phone today this is first time I'm installing a Custom Rom.
There is an Instruction in the Rom I want to install. Do factory reset (While in Recovery I think.)

Just flash superwipe first, after that, the rom and something else if needed, if you are going for sense4, manually wipe everything from recovery, except the sd.
And that's it,......... uuu one more thing, backup your messages with some app, if you have important ones.

Thanks for the info!
Yeah I'm going with sense4.
Last question what is the minimum memory card size in doing the partition, I have a 4GB Micro SD is that enough?

Personally I haven't tried sense 4 (neither of them), but from what I read, you need at least 1GB ext3 or ext4(if I'm wrong somebody to correct me). And that's it. If you don't know how to make a partition check out my signature, there should be tutorial about that.

So what is the Custom Rom your using maybe I'll use that.

I'm on aokp (by legen_dary), but that's irrelevant, if you like sense, give it a try, sense roms are cool, they are just not my cup of beer. And whatever you choose to install, should be something that you like, anyway installation process for 95% of roms(sense or no sense) is pretty much the same, so if sense got your atention, go for it!

Ok thanks man you really made my day!

+1 to whatever shortyoko said upto now.. And one more point to be added iz that use yannou's recovery ( r recovery in jaggy jaggs tutorial) for flashing sense roms as they mount sd ext while flashing properly.. Other recoveries have some issues.. Though I tried with twrp to flash build 6.. And it worked..
I'm on my tab

Thank you for that Red Devil!

Stuck in a bootloop
I searched a lot on the forum tried going back to the stock ROM, but still stuck in bootloop need help

Details buddy, details. Also in my signature are two versions of stock rom, check them out