Develop Bugs

[HELP] Problem with flashing Myn’s Warm TwoPointTwo RLS 5

Ok heres the deal.. Im a noob and have only flashed one rom since root so im real fresh to this.
My set up is as follows: rooted with unrevoked running cyanogen 6.1.2 i flashed amen ra 2.3. I dowloaded the Rom and Radio/Wimax updates and flashed according to the instructions on Myn's OP.
It boots fine but after about 60 seconds of being booted i get roughly 4-6 force close notifications. One for the market, messages, media, android process and the others i cant remember. Any ideas of what went wrong?
I really like the look and feel of this rom so I REALLY REALLY need all the help i can get on this.
Please help..

tobiasunruh said:
Ok heres the deal.. Im a noob and have only flashed one rom since root so im real fresh to this.
My set up is as follows: rooted with unrevoked running cyanogen 6.1.2 i flashed amen ra 2.3. I dowloaded the Rom and Radio/Wimax updates and flashed according to the instructions on Myn's OP.
It boots fine but after about 60 seconds of being booted i get roughly 4-6 force close notifications. One for the market, messages, media, android process and the others i cant remember. Any ideas of what went wrong?
I really like the look and feel of this rom so I REALLY REALLY need all the help i can get on this.
Please help..
Click to expand...
Click to collapse
You did a full wipe prior to flashing right? Maybe try re-wiping everything, then flashing the rom again.

Do you mean a all user data/factory reset? If so then no. I wiped data, cache & dalvik tho. I also tried three different sources for the rom download and flashed all three and got the same results each time.

When you flash a new rom, you should always wipe EVERYTHING: cache, data, factory reset, and dalvik. Try doing it again with wiping all of this first.

tobiasunruh said:
Ok heres the deal.. Im a noob and have only flashed one rom since root so im real fresh to this.
My set up is as follows: rooted with unrevoked running cyanogen 6.1.2 i flashed amen ra 2.3. I dowloaded the Rom and Radio/Wimax updates and flashed according to the instructions on Myn's OP.
It boots fine but after about 60 seconds of being booted i get roughly 4-6 force close notifications. One for the market, messages, media, android process and the others i cant remember. Any ideas of what went wrong?
I really like the look and feel of this rom so I REALLY REALLY need all the help i can get on this.
Please help..
Click to expand...
Click to collapse
Your EVO needs a WIPE!! I prefer to use C's Format All Zip TWICE as well as separately wipe Cache and Dalvik TWICE. After first boot, I like to reboot to recovery and wipe the Dalvik two more times. Reboot, fix permissions, reboot and you should be good to go.

Thanks guys.. I will try that right now and let you know how it turns out..
Can any one tell me where to find the cs format?
And do I need to format my sd card?
Sent from my PC36100 using XDA App

tobiasunruh said:
Thanks guys.. I will try that right now and let you know how it turns out..
Can any one tell me where to find the cs format?
And do I need to format my sd card?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Hey man. Attatched is a copy of Calkulin's Format all. You flash it in recovery, and it wipes everything. It ensures a solid wipe. Use your recovery to wipe data/factory reset, cache, and davlik cache two times each. Then flash this zip in recovery. Then reflash the ROM. That should do the trick for you, Myn's runs good and clean!
Edit: And no, you do not need to format your SD card.

I wanna say thanks to all you guys for your help. I have it installed and running great.
If any of you have any recommendations for mods I'm open to suggestions..

CM7 final bootloop

So I have a rooted (latest unrevoked) EVO with stock ROM. Radio is the current version so I did not need to flash a new radio. I have the rom backed up with rom manager and also a Titanium Backup.
I download Cm7-final with Rom Manager and proceed to flash it. All appears well until it loads and I'm stuck in CM7 splash bootloop and never get into the actual OS/homescreen. I boot to recovery and restore my prior rom backup, luckily all is fine.
My question is what have i done wrong? I read the EVO CM7 Wiki and it looks like I followed the instructions correctly. Do I need to ditch using RomManager and try it manually? Any suggestions on why I got this bootloop?

i had the same problem when i tried to update on the g2. i backed up the phone and wipe data and caches and flashed again the it worked you might have to do it acouple of times
Sent from my SGH-T959 using XDA App

KNguyen104 said:
i had the same problem when i tried to update on the g2. i backed up the phone and wipe data and caches and flashed again the it worked you might have to do it acouple of times
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Using the RomManager interface I chose to Wipe Data and Cache and also chose the gapps package to install. I guess I could try it again but I was mystified why it didnt work since I "thought" it was so simple.

If you're coming from a sense rom, wipe cache, data, dalvik, system, boot, basically everything but the sd card. After that, flash cyanogenmod, then gapps, then start the phone.
Sent from my hand with XDA Premium installed

snowboarda42 said:
If you're coming from a sense rom, wipe cache, data, dalvik, system, boot, basically everything but the sd card. After that, flash cyanogenmod, then gapps, then start the phone.
Sent from my hand with XDA Premium installed
Click to expand...
Click to collapse
I'm an android noob, you'll have to forgive me. I thought when I selected "wipe data and cache" prior to flashing CM7 in the RomManager interface that it meant it would wipe all of that.
So I need to manually wipe everything except the card? Also, a secondary question, will any of this jeopardize the ability to restore my currently backed up stock sense rom if **** hits the fan?

Alpine- said:
I'm an android noob, you'll have to forgive me. I thought when I selected "wipe data and cache" prior to flashing CM7 in the RomManager interface that it meant it would wipe all of that.
So I need to manually wipe everything except the card? Also, a secondary question, will any of this jeopardize the ability to restore my currently backed up stock sense rom if **** hits the fan?
Click to expand...
Click to collapse
No it won't as long as you have a nandroid. Look up the "VR Superwipe," and flash it. I'd recommend booting into recovery manually and doing this. Wipe cache and dalvik after flashing the superwipe for good measure. Finally flash the ROM.
Sent from my PC36100 using Tapatalk

Alpine- said:
So I have a rooted (latest unrevoked) EVO with stock ROM. Radio is the current version so I did not need to flash a new radio. I have the rom backed up with rom manager and also a Titanium Backup.
I download Cm7-final with Rom Manager and proceed to flash it. All appears well until it loads and I'm stuck in CM7 splash bootloop and never get into the actual OS/homescreen. I boot to recovery and restore my prior rom backup, luckily all is fine.
My question is what have i done wrong? I read the EVO CM7 Wiki and it looks like I followed the instructions correctly. Do I need to ditch using RomManager and try it manually? Any suggestions on why I got this bootloop?
Click to expand...
Click to collapse
I had the same issue....although mine have been caused by restoring system data.
What I did is manually DL the rom, boot into recover, wiped cache/dalvic, flashed from zip (Both CM7 and the proper GAPPS file) and it worked.

eventer289 said:
No it won't as long as you have a nandroid. Look up the "VR Superwipe," and flash it. I'd recommend booting into recovery manually and doing this. Wipe cache and dalvik after flashing the superwipe for good measure. Finally flash the ROM.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
nandroid? So the RomManager rom backup I created isnt sufficient? I also have a full Titanium Backup saved too. Why Nandroid? I was under the impression this was just a similar app to Titanium - wrong?
Thanks for the input guys.

Alpine- said:
nandroid? So the RomManager rom backup I created isnt sufficient? I also have a full Titanium Backup saved too. Why Nandroid? I was under the impression this was just a similar app to Titanium - wrong?
Thanks for the input guys.
Click to expand...
Click to collapse
So wait, still getting the loops?

teh roxxorz said:
So wait, still getting the loops?
Click to expand...
Click to collapse
I have no tried since I got all these suggestions. Sorry for the confusion. I suspect manually wiping and manually installing will work.

Alpine:
When I first started flashing stuff I relied on the Clockwork app to do everything. I used it to flash roms and clear/wipe data and cache. However, after running into problems like yours I started doing it manually.
What I started doing was booting into RECOVERY (i know it sounds scary but it really isn't) A little off topic but there is a great app that I think every rooted user should use, it's called: Reboot Control Widget It only costs a measly $1 in the Market but it's well worth it. Basically you put the widget on the desktop and click on it. You are then given the option to Reboot your phone, Hot Boot (fast reboot), boot into Recovery, Bootloader or Shut Down. Best dollar you will ever spend on an app.
So anyway, l strayed from my point. The problem you are experiencing is partially due to not having fully wiped your phones data/cache. I know you think you did it through the Clockwork app but from experience it doesn't work that well. There is a "flashable" file called Calkulin's Format All. It is in the DEV section posted in Calkulin's Rom section. It will clear everything except the contents of your SD card.
1. Boot into RECOVERY
2. find: INSTALL ZIP FROM SDCARD
3. select the Calkulin's Format ALL.zip file (your phone will be totally clean after this)
4. Again, choose INSTALL ZIP FROM SDCARD
5. Select the ROM you want to flash. (If it is a Cyanogen based ROM you will have to flash the appropriate Google Apps file after flashing the ROM. If flashing a Sense ROM the Gapps file is not necessary)
6. Flash Gapps file (Google apps if necessary)
7. Once this is done select REBOOT SYSTEM NOW
I feel confident that if you follow those steps you won't run into any bootloops!

I have added the Format All.zip file that I mentioned in my last post.
Little advice:
- take the time to do a Nandroid before flashing a new rom
- use Titanium to restore only the apps w/o the data. I know it's nice to restore everything the way you had it on the last rom but from my experience this has led to instability in the new rom. Also from my experience when you are on a SENSE rom and use Titanium to backup your files and data when you install a AOSP (like CM) rom and try to restore those files and data it won't even let you. Just something to keep in mind if you are switching between CM to Sense or vice versa.

Alpine- said:
I have no tried since I got all these suggestions. Sorry for the confusion. I suspect manually wiping and manually installing will work.
Click to expand...
Click to collapse
Yes it should.
Manually wipe you factory/data, cache, dalvik, then flash the rom with the latest gapps and you'll be good.

SantinoInc said:
Alpine:
When I first started flashing stuff I relied on the Clockwork app to do everything. I used it to flash roms and clear/wipe data and cache. However, after running into problems like yours I started doing it manually.....
Click to expand...
Click to collapse
Wow, great post. Very informative and detailed, thanks a lot.
So why is creating a nandroid backup better than the ROM backup function in RomManager? I restored that rom once and it worked flawlessly. How does nandroid differ from the rom backup created in RomManager?

when you use clockwordmod recovery to wipe your phone the dalvik doesn't wipe with the wipe option you see on the main screen, i belive you will see the option to wipe it in the advanced menu

Alpine- said:
Wow, great post. Very informative and detailed, thanks a lot.
So why is creating a nandroid backup better than the ROM backup function in RomManager? I restored that rom once and it worked flawlessly. How does nandroid differ from the rom backup created in RomManager?
Click to expand...
Click to collapse
They are the same. ROM Manager boots you into recovery and nandroids for you. People have mixed experiences with ROM Manager. From my experience it is best just to boot manually into recovery and take care of all your flashing and wiping there.
Sent from my PC36100 using Tapatalk

[Q] Salvage Mod 1.2.1 won't boot.

I just tried flashing salvage mod and its gapps and it wouldn't boot either time. I also cleared all cache. Anyone know what I can do?

it is salvage mod 1.2.1.

JerenOtt said:
I just tried flashing salvage mod and its gapps and it wouldn't boot either time. I also cleared all cache. Anyone know what I can do?
Click to expand...
Click to collapse
What ROM were you on before you flashed Salvage Mod? If it was a sense rom, you need to perform a full wipe (data/factory reset, cache, dalvik cache, boot, system) prior to flashing the new rom. When you said you cleared 'all cache', do you also mean you cleared dalvik cache as well? What recovery are you currently using? I'm on salvage 1.2.1 right now, and I've never had a problem booting it. When you say it won't boot, what does it do? Does it boot loop, or does it hang at the splash screen (white htc evo 4g screen)? The more info the better. I'd basically suggest doing a full wipe though, and try again.

k2buckley said:
What ROM were you on before you flashed Salvage Mod? If it was a sense rom, you need to perform a full wipe (data/factory reset, cache, dalvik cache, boot, system) prior to flashing the new rom. When you said you cleared 'all cache', do you also mean you cleared dalvik cache as well? What recovery are you currently using? I'm on salvage 1.2.1 right now, and I've never had a problem booting it. When you say it won't boot, what does it do? Does it boot loop, or does it hang at the splash screen (white htc evo 4g screen)? The more info the better. I'd basically suggest doing a full wipe though, and try again.
Click to expand...
Click to collapse
I was on stock rooted before this. I did clear dalvik cache but I need to do a factory reset like you said. Thanks.

I tried that and it's still doing the same thing. It just sits at a lit up black screen. Any other suggestions?

JerenOtt said:
I was on stock rooted before this. I did clear dalvik cache but I need to do a factory reset like you said. Thanks.
Click to expand...
Click to collapse
No problem man. It will boot up after a doing a full wipe, most likely.

JerenOtt said:
I tried that and it's still doing the same thing. It just sits at a lit up black screen. Any other suggestions?
Click to expand...
Click to collapse
Can you boot into the bootloader? Power off your device. Simultaneously press the DOWN volume button and the power button until your device starts. After a short pause, a few lines of text should scroll across the screen and then you will see a few options. One of the options will be recovery. Anyway, at the top of the screen, you should see either S-ON or S-OFF. Hopefully, it displays S-OFF. Anyway, select recovery from the set of options and then, as k2buckley has instructed, go to the wipe menu and wipe EVERYTHING except the SD card itself. When you're done, do not reboot. Go to the flash menu and flash the rom you want to flash. Do not flash the gapps zip yet. Reboot after flashing the rom. I want to make sure you're able to boot into the homescreen. If you're successful, reboot into recovery, wipe cache & dalvik and then flash the gapps.zip. afterwards, reboot. When you're all setup, go back I to recovery and make a nandroid backup.
posting & replying via the XDA Premium app.

also, make sure you got the full ROM, not just the patch for going from 1.2 to 1.2.1. I did that

I was having similar issues, mine went into a boot loop about twice before getting hung up at the initial setup with FCs. I was coming from CM7 Nightly 41 that was acting weird with FC's, I always double wipe cache/dalvik/factory reset. I thought that I might have had a bad download so I re-downloaded, wiped and flashed. I couldn't get past the initial setup so I went back to Ultimate Droid and have been running that for the last 4 days or so with out any major problems except for the Facebook update dicking things up and one random reboot that I had today... I really want to give Salvagemod a shot though since it's Evo-centric.

still not working for me
hey guys... i been trying to boot into salvage mod for the past 2 days... i get it to install just fine i do get the salvage screen up too...
then when the rom is supposed to be loaded up i get the Android dude with emergency call and a crash u keep pressing ok then it goes away and comes back right away... i just wiped everything again and reflashed it and now i am stuck with salvage screen re looping..
any help would be appreciated
thanks

The OP's problem was solved in a second thread by following the below instructions:
Download a fresh copy of both amon RA v2.3 (PC36IMG.zip) and Salvage-Mod 1.2.1 and place both on the root of your SD card. Make sure there is no other file named PC36IMG.zip. on the root of your card. If there is, put that particular file in a folder. Now shutdown your device. Boot into the bootloader screen. The bootloader will automatically detect the PC36IMG.zip file and prompt you to install. Follow the prompts to install. Installation should take less than 10 seconds. Afterwards, reboot into your new recovery. Go to the wipe menu and wipe everything except the SD card. Do not reboot. Go to the flash menu and flash Salvage-Mod. This *should* work.
posting & replying via the XDA Premium app.

dougjamal said:
The OP's problem was solved in a second thread by following the below instructions:
Download a fresh copy of both amon RA v2.3? (PC36IMG.zip) and Salvage-Mod 1.2.1 and place both on the root of your SD card. Make sure there is no other file named PC36IMG.zip. on the root of your card. If there is, put that particular file in a folder. Now shutdown your device. Boot into the bootloader screen. The bootloader will automatically detect the PC36IMG.zip file and prompt you to install. Follow the prompts to install. Installation should take less than 10 seconds. Afterwards, reboot into your new recovery. Go to the wipe menu and wipe everything except the SD card. Do not reboot. Go to the flash menu and flash Salvage-Mod. This *should* work.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Glad you got him going Doug. I had asked him to use RA in a PM, and he responded that he liked clockwork and rom manager better, and wouldn't use RA, lol. I'm glad you convinced him otherwise.
Sent from my PC36100 using XDA App

lol....Happy Easter, my friend...
posting & replying via the XDA Premium app.

dougjamal said:
lol....Happy Easter, my friend...
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Thank you Doug, happy Easter to you as well.
Sent from my PC36100 using XDA App

dougjamal said:
The OP's problem was solved in a second thread by following the below instructions:
Download a fresh copy of both amon RA v2.3 (PC36IMG.zip) and Salvage-Mod 1.2.1 and place both on the root of your SD card. Make sure there is no other file named PC36IMG.zip. on the root of your card. If there is, put that particular file in a folder. Now shutdown your device. Boot into the bootloader screen. The bootloader will automatically detect the PC36IMG.zip file and prompt you to install. Follow the prompts to install. Installation should take less than 10 seconds. Afterwards, reboot into your new recovery. Go to the wipe menu and wipe everything except the SD card. Do not reboot. Go to the flash menu and flash Salvage-Mod. This *should* work.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
hey thanks a bunch doug... that was the issue darn clockwork..lol.. got it running so far so good
so after i got it running decided to install the gapps stuff too from recovery...and there goes my phone again back to android with emergency call only... going to try installing again without gapps...any tips let me know please..
thanks

Did you wipe cache and dalvik before flashing gapps? Also, are you sure you're using the correct version of gapps for whichever rom you're on?
Sent from my PC36100 using XDA App

k2buckley said:
Did you wipe cache and dalvik before flashing gapps? Also, are you sure you're using the correct version of gapps for whichever rom you're on?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
yup did everything... weird but i got it working now..did everything the same way as b4...its really sweet.. and really fast... thanks a bunch for the help

nxtstep said:
hey thanks a bunch doug... that was the issue darn clockwork..lol.. got it running so far so good
so after i got it running decided to install the gapps stuff too from recovery...and there goes my phone again back to android with emergency call only... going to try installing again without gapps...any tips let me know please..
thanks
Click to expand...
Click to collapse
You're very welcome, my friend. I'm glad I was able to help. Take care and have a great day....
posting & replying via the XDA Premium app.

k2buckley said:
What ROM were you on before you flashed Salvage Mod? If it was a sense rom, you need to perform a full wipe (data/factory reset, cache, dalvik cache, boot, system) prior to flashing the new rom. When you said you cleared 'all cache', do you also mean you cleared dalvik cache as well? What recovery are you currently using? I'm on salvage 1.2.1 right now, and I've never had a problem booting it. When you say it won't boot, what does it do? Does it boot loop, or does it hang at the splash screen (white htc evo 4g screen)? The more info the better. I'd basically suggest doing a full wipe though, and try again.
Click to expand...
Click to collapse
You're a genius. I was doing a data/factory reset, cache, and dalvik, but not boot and system. When i did those, it worked. Thanks!

[Q] can't run any new rom, hangs at white htc incredible screen on boot

I rooted the incredible using unrevoked, no problem.
Installed and ran root apps, no problem, backed up everything using titanium backup and rom manager (nandroid) and so forth, installed cw recovery 3.0.0.8.
When I install the skyraider 4 rom from rom manager, it reboots and installs, but then when it reboots again it hangs at the white htc incredible screen (and I've let it wait as long as a half an hour). I have to take out the battery to be able to reboot it.
I can boot back to recovery and then re-install and boot back to the stock rooted rom just fine. But I can't get a new rom installed and working.
I've looked at previous threads about this problem:
http://forum.xda-developers.com/showthread.php?t=1038402
http://forum.xda-developers.com/showthread.php?t=1023358
http://forum.xda-developers.com/showthread.php?t=991953
http://forum.xda-developers.com/showthread.php?t=739646
http://forum.xda-developers.com/showthread.php?t=620621
and several other threads on other sites.
The only suggestions to come out of those, other that starting over from scratch (which I've done multiple times now), were to reformat the sd card, which I've also done, and to downgrade to cm recovery 2.5.1.2. Rom manager only shows versions as old as 3.0.0.5. I have put the PB31IMG.zip file on the sd card and loaded that before to help recover but I don't see how that helps with installing a new rom.
Any other suggestions? The main reason I even need a new rom is because bluetooth doesn't work in the stock rom (known issue: http://community.htc.com/na/htc-forums/android/f/91/p/2336/8570.aspx )

It sounds like you are not wiping cache and Davlik (in advanced). The constant reboot of the white screen is a classic symptom of not performing a cache and Davlik wipe

patsfan1130 said:
It sounds like you are not wiping cache and Davlik (in advanced). The constant reboot of the white screen is a classic symptom of not performing a cache and Davlik wipe
Click to expand...
Click to collapse
appreciate your help, yeah I've been doing that everytime in rom manager. I tried it several times manually in cm recovery, too, and still the white screen.
I'll just see if verizon can exchange it, or else I'll sell it for another phone with working bluetooth.

Might try reverting to the 2.5.1.2 recovery as I've heard the 3.x.x.x ones don't wipe consistently.
Sent from my ADR6300 using XDA App

when im change roms im not use Rom manager,im just use rom manager for Backup Current Rom.I use quickboot for install a new Rom
1.open quickboot
2.choose recovery
3.wipe date/factory reset
4.drop down to yes delete all user data
5.go back to the first panel and choose advance(5 and 6 optional)
6.and then wipe Dalvik Cache
7.install zip from sd card.
8.good lock,(xdadevelopers and me are not responsable for any damage in your cell.)
Im running the skyrider 4.0 and is a wonderfull Rom,highly recommended.

when im change roms im not use Rom manager,im just use rom manager for Backup Current Rom.I use quickboot for install a new Rom
1.open quickboot
2.choose recovery
3.wipe date/factory reset
4.drop down to yes delete all user data
5.go back to the first panel and choose advance(5 and 6 optional)
6.and then wipe Dalvik Cache
7.install zip from sd card.
8.good lock,(xdadevelopers and me are not responsable for any damage in your cell.)
Im running the skyrider 4.0 and is a wonderfull Rom,highly recommended.

k_nivesout said:
Might try reverting to the 2.5.1.2 recovery as I've heard the 3.x.x.x ones don't wipe consistently.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
.
There is a flash of CWM 2.5 that temporarily lets you use that to flash the rom then when you reboot it will revert back. Try that.

Noob here, needing help about his rooted Desire

HI
well I rooted my desire using the Full update Guide for the HTC desire (GSM) on the cyanogenmod wiki site.
that installed fine, after a while i decided to download and flash one of LEEDroids ROMS
the installation went fine, but when it started to boot up the sequence kept on repeating.
not knowing what was happening, I went to the recovery memory and used the wipe option.
Eventually I found the restore option, and bought back the cyanogenmod rom.
I have tried many other ROMS and the result is the same, the boot up sequence keeps on repeating...
NEED HELP !!!

yhq92 said:
HI
well I rooted my desire using the Full update Guide for the HTC desire (GSM) on the cyanogenmod wiki site.
that installed fine, after a while i decided to download and flash one of LEEDroids ROMS
the installation went fine, but when it started to boot up the sequence kept on repeating.
not knowing what was happening, I went to the recovery memory and used the wipe option.
Eventually I found the restore option, and bought back the cyanogenmod rom.
I have tried many other ROMS and the result is the same, the boot up sequence keeps on repeating...
NEED HELP !!!
Click to expand...
Click to collapse
Follow the link in my sig for the newbie's guide. It explains everything with videos.

Pipusz said:
Follow the link in my sig for the newbie's guide. It explains everything with videos.
Click to expand...
Click to collapse
eerr, what link? LOL
make sure to wipe dalvic cache (from advanced options) and format everything i.e. boot, system, userdata, cache and sd-ext (from mounts and storage) (apart from sdcard!!!!!) (IF you're using clockworkmod recovery), then proceed to install a new ROM.

bortak said:
eerr, what link? LOL
make sure to wipe dalvic cache (from advanced options) and format everything i.e. boot, system, userdata, cache and sd-ext (from mounts and storage) (apart from sdcard!!!!!) (IF you're using clockworkmod recovery), then proceed to install a new ROM.
Click to expand...
Click to collapse
I have 5 links in my sig and I don't think they are hidden...

Thnx
Does anyone have a good ROM to recommend? Id prefer one with. HTC sense 3.0

The first ROM I used was Android Revolution. My wife is still using it. She can't live without sense. Search for it on here.
--
Phone: HTC Inspire 4G
ROM: Cyanogen(mod) 7 Nightly
Launcher: Zeam
Keyboard: Swype
App: Tapatalk

Hi yhq92,
i followed this link and found it was very straight forward, also has a few of linkslovesandroids fav's, i chose Robo's Rcmix s, becomes very addictive now want to swap it again lol
http://forum.xda-developers.com/showthread.php?t=1016084

bortak said:
eerr, what link? LOL
make sure to wipe dalvic cache (from advanced options) and format everything i.e. boot, system, userdata, cache and sd-ext (from mounts and storage) (apart from sdcard!!!!!) (IF you're using clockworkmod recovery), then proceed to install a new ROM.
Click to expand...
Click to collapse
yeahh so I did that then installed the RCMixHD it finishes booting but now the screens stuck on this ( see attached image)
HELP

You have to be patient on first boot, it can take 10-15 minutes before it progresses beyond that stage.

Or you failed repartitioning sd card.
Do you have 1gb+ ext3/4 partition?
Sent from my HTC Desire using XDA App

Yeah first boot took ages for me to the point I was gonna unplug, glad I didn't, not sure if you get the notifications bar on boot though so think something might not be right! I'd restore and try again, like K3lcior said check partitioned correctly, I kept watching the video's on linkslovesandroids link until I had it in my head,

Right, I'll. Have to check that.
Thnx for the advise