Develop Bugs

[Q] Bootloop help

I'm having issues with a bootloop on the incredible after rooting using unrevoked 3 and making the mistake of choosing cyanogenmod as the recovery because I'm incredibly new at this. Now granted this isn't an issue, I have root access now and I'm able to assign superuser and the phone boots to what looks like the stock rom. However, I wanted to flash cyanogen 7 rc2 and it's giving me a lot of issues when I try to access the clockworkmod recovery screen. I downloaded the rommanager from the market and flashed the recovery to clockworkmod 3.0.0.8 as per a wiki online and tried to boot to recovery. from there it hits the HTC incredible screen, then flashes every 3 seconds rather than showing the green text it's supposed to show.
I still have S-on and unrevoked won't run properly again. Tried running the factory reset and it's another bootloop. I tried going through the steps for a "manual recovery file flash via cyanogen's wiki, but I'm running into errors.
Summary:
unrevoked 3.32 completed successfully even using the cyanogenmod rom as the recovery file.
Have root access, S-on, radio version ~.7.28
Can't flash back to stock due to bootloop
Can't factory reset due to bootloop
Can't get to clockworkmod recovery screen due to bootloop
phone able to boot to main screen with original
Ideal solution: get to clockworkmod recovery screen and install C7RC2
Any help appreciated!

Why do you think using ClockworkMod was a mistake? It's one of the better AOSP ROMs out there.
It sounds to me like you're probably going to have to download one of the stock RUUs to completely revert your phone to stock. You might have a corrupted recovery. You can't flash ClockworkMod or an alternative recovery via RomManager?

oh don't get me wrong, my huge problem here is that I can't get into recovery, and I didn't load clockworkmod initally, but it is (as rom manager says) my recovery image and it's just not working at all.
I tried going with a RUU and it wouldn't get into bootloader properly (just shows HTC on the screen till the the ruu times out) I'll try on a 32 bit machine when I get home. I was originally able to flash on that and unrevoked was giving me issues till I did a 32 bit xp attempt. Thanks for the response!

whoops, forgot to address your last point. Tried another version of clockwork and the RA_GNM 1.8.1 and neither stopped it from bootlooping rather than recovery screen.

HTCP2newb said:
I'm having issues with a bootloop on the incredible after rooting using unrevoked 3 and making the mistake of choosing cyanogenmod as the recovery because I'm incredibly new at this. Now granted this isn't an issue, I have root access now and I'm able to assign superuser and the phone boots to what looks like the stock rom. However, I wanted to flash cyanogen 7 rc2 and it's giving me a lot of issues when I try to access the clockworkmod recovery screen. I downloaded the rommanager from the market and flashed the recovery to clockworkmod 3.0.0.8 as per a wiki online and tried to boot to recovery. from there it hits the HTC incredible screen, then flashes every 3 seconds rather than showing the green text it's supposed to show.
I still have S-on and unrevoked won't run properly again. Tried running the factory reset and it's another bootloop. I tried going through the steps for a "manual recovery file flash via cyanogen's wiki, but I'm running into errors.
Summary:
unrevoked 3.32 completed successfully even using the cyanogenmod rom as the recovery file.
Have root access, S-on, radio version ~.7.28
Can't flash back to stock due to bootloop
Can't factory reset due to bootloop
Can't get to clockworkmod recovery screen due to bootloop
phone able to boot to main screen with original
Ideal solution: get to clockworkmod recovery screen and install C7RC2
Any help appreciated!
Click to expand...
Click to collapse
Did you try getting to recovery manually power off the phone while its off press power and volume down at the same time you should be in hboot use the volume button to scroll down boot into recovery.....
Sent from my Incredible using XDA App

I don't think unrevoked finish all The way because you should be s-off did you wait until it said "done"..... or did you stop when it said "this is a triumph"
Sent from my Incredible using XDA App

Okay, from a 32 bit system has resolved the flashing back to a stock rom, I will update as to whether I can get into recovery and will wait until I am told "triumphant" this time around.
Will post an update in a bit if this was all that was necessary to fix the issue. Thank you all to have posted so far, please post if you think I'm missing something else.

HTCP2newb said:
Okay, from a 32 bit system has resolved the flashing back to a stock rom, I will update as to whether I can get into recovery and will wait until I am told "triumphant" this time around.
Will post an update in a bit if this was all that was necessary to fix the issue. Thank you all to have posted so far, please post if you think I'm missing something else.
Click to expand...
Click to collapse
No you need to wait till it says done sorry you misunderstood me......let it go till it says done and it stops completely..... because the last thing it does is flash the recovery
Sent from my Incredible using XDA App

Did you try flashing a recovery through hboot?
Sent from my ADR6300 using XDA App

Okay, problem totally resolved. basically what happened was that there was an incomplete unrevoked process for whatever reason or another. I repaired by downloading the RUU off the HTC website and flashing back to stock. That generated an error of "your firmware is too new" which is available elsewhere in XDA, basically solved by going into hboot and factory resetting.
Once I had the factory reset completed, I used a 32 bit system to unrevoke the phone (after setting debugging to on in applications > developer settings >debugging on) then I was able to properly boot into recovery. I recommend Clockworkmod update to 3.0.0.8 in Rom manager, but I used 2.5 and didn't have much of an issue. I backed up and the wiped the memory and cache and installed 7r2 without an issue.
The phone is WAY more stable now (thanks to all the hard work at Cyanogen! Thank you also to everyone who posted here!) Pandora doesn't randomly cut songs in half and battery life seems to have improved. Whether that was verizon's crap or I went market-crazy and had waaaay too many apps syncing... I can't say.
Thank you everyone again!

need Recovery for HBoot 93 SLCD

Hi,
I have a TELUS HTC Desire that was already rooted when I got it.
It has HBOOT 0.93
I didn't know that my phone was SLCD so when I used ROM Manager to flash recovery, it messed up my recovery.
If I go into hboot, and press down arrow to boot into recovery, I get the black screen with the little phone and the red triangle with the exclamation mark.
I was desperate enough to try the ClockworkMod Recovery for the HBOOT 0.83 (ClockworkMod Recovery v2.5.0.1 SLCD)
from hxxp://forum.xda-developers.com/showthread.php?t=748618
flashed that on with UnrEVOked but didn't work. Recovery is still messed up.
I googled and searched for a week to find something for HBOOT 0.93 but I never find anything. Everything is for 82, 83 and 92. There are other people who asked about 0.93 in other threads but there are never answers to them.
Does anyone know of a proper ClockwordMod recovery img or ANY recovery img I can flash for my HBOOT 0.93
My phone is already android 2.2 but i would really like to flash to LeeDroid
Should I reflash my phone with the RUU to get rid of any dmg done? The only thing i'm afraid of is that my phone will be unrooted because of the RUU reflash and I can't find a way to root it.
If it's not possible to use UnrEVOked or Rom Manager to install LeeDroid because of HBOOT 0.93, I'm willing to manually do it.
But will the LeeDroid flash properly onto my phone if it's HBoot 0.93?
Does the flashboot thing when i boot into the HBOOT work for installing custom ROMS if I can't get into recovery? I noticed it will load images...but not sure exactly what the fastboot thing is suppose to do.
Thanks!!

HBOOT 0.93 is not the problem, neither is your SLCD. Use fastboot to flash your recovery, I suggest use either AmonRa 2.0.1 or CWM 2.5.1.8.
CWM from ROM Manager isn't the best recovery for your HBoot as I think it flashes 2.5.0.7 which is no good on your HBoot.
You can't flash a ROM from fastboot, you need recovery. Once you've done that, LeeDrOiD will work fine on your setup, but I would suggest you study up a lot more before proceeding, for one thing, it's easy to find a lot of info on HBoot 0.93 on this forum, secondly, get to know fastboot etc as you needs to know this for when things go wrong with cheat/easy methods like ROM Manager.
Take your time, be confident you know what you are doing it before you do it, you don't want to brick your phone.

Both of you need to know quite a bit more, but especially the OP...
But no he can of course not flash an unsigned recovery from fastboot without being s-off, and from the sound of the first post I'm confident he's not.
ghalalb is right though when he states that this has nothing to do with your bootloader version or slcd, and i really can't imagine how you can get the simple instructions on here wrong, but please simply use unrevoked via usb. It comes preloaded with a perfectly fine recovery for you, and also i believe you should really reconsider the decision to hack your phone with this little knowledge on the subject.
Also 2.5.0.7 vs 2.5.1.8 has nothing to do with hboot versions.. Both will work fine if flashed correctly, but the problem with just making rom manager flash the recovery is, that it is not quite up to date, so it does not actually flash anything. It just downloads an update.zip file, which loads the recovery when flashed. This fixed the problem of not being able to flash a custom recovery back before unrevoked came around. And to correct you on another thing you got wrong, yes you can actually flash a zip file containing something like a rom from fastboot if you are s-off. It will probably just not work exactly the same way, as the recoveries does.

That's interesting that you say hboot version and slcd has nothing to do with the ClockworkMod when other threads are very specific about which clockworkmod version you should use depending on your hboot and if your phone is slcd or not.
Also last time I did an update to the phone, it just used the fastboot. Didn't go into recovery.
I followed the exact instructions for unrevoked but an error occurrs when it tries to unroot...All I wanted to do was flash the recovery and not unroot the phone since it's already unrooted. So probably that's why it was having problems. But the recovery was still messed up after unrevoked did it's work.
I wonder if part of the problem is because I'm using a test image and not the actual production image for the phone. Which is probably another reason why the phone was already unrooted.
I'll try to reflash my phone using the RUU for a production image and try Unrevoked again just so everything is clean from the start

Trust me it doesn't matter. The only problem was on slcd phones back when they first came out, where cwm didn't contain the drivers for the new screen.
That is why it says it's for 0.83, as back then 0.83 was equal to slcd and all amoled models had come with 0.75 or 0.80. But now after the newer updates everyone is on 0.93 or so, and all newer cwm recoveries will work for both amoled and slcd. So no there is not a specific recovery for every bootloader, and there is no way a flash from rom manager messed your recovery up, as it never flashes anything.
And i think you might need to slow down and think about what you are doing? Because you talk about unrooting with unrevoked, and unrevoked will probably try to root your phone If you use unrevoked correctly you will have it working fine.
Also you say last time you updatet it, it used fastboot? updatet it officially? As then there is a reason you have the stock recovery. But try using the ruu and then go back to rooting using unrevoked or just keep it stock, as it might not be a good idea trying something without knowing what it does.
edit: and the screen you get with the phone in a triangle with an exclamation mark doesn't mean anything is wrong. It's just the stock htc recovery... If you press vol-up+power(or vol-down+power i don't remember) when you see this screen, you get a simple menu, which lets you flash update.zip and erase data.

mortenmhp said:
edit: and the screen you get with the phone in a triangle with an exclamation mark doesn't mean anything is wrong. It's just the stock htc recovery... If you press vol-up+power(or vol-down+power i don't remember) when you see this screen, you get a simple menu, which lets you flash update.zip and erase data.
Click to expand...
Click to collapse
Thanks for your response I thought that the triangle screen was bad since I tried the volume stuff and I couldn't get to the screen.
But if that's the stock htc recovery, then that means the clockworkmod recovery wasn't flashed properly?
I will try the keys again when i get to the recovery state later.
Actually I was having problems with UnrEVOked because my phone was ALREADY rooted. So it was trying to do something that was already done which is probably why it failed. I only needed unrevoked to flash the recovery...I didn't need it to do anything else but the recovery.
What I have on my phone right now is not the official load. It has test keys and crap in it....
Anyways, I'll see if I can get into the recovery menu properly before doing the RUU flash to have a clean start.

Ok Unrevoked should work fine anyway though. It just flashes a recovery and the su binary plus the superuser app. So if you are rooted it will just overwrite them. Your problem is far more likely to be a driver problem.
I rooted the old way as well(the one only allowing test keys signed roms) and then i used fake flash from rom manager until alpharev s-off came along, and now i just flash everything but roms from fastboot, it's far easier.

driver problem?
I followed the unrevoked instructions and my computer recognizes the phone while it's in bootloader
i can also adb shell into it when it's just normally powered on etc
oh and to answer previous question, yes i updated to 2.2 using fastboot
i put IMG99.zip onto my sdcard
powered on while holding the volume down for fastboot
it went and found the image on my sd card and grabbed it...and asked if I wanted to update...and viola...2.2
my phone was...2.0 or 2.1 when i first got it i think...i forgot what it was before 2.2
that's why i asked if anyone just stuck a custom rom into their SD card and tried using fastboot before....seems like everyone these days use things like rom manager, unrevoked etc >_<
I would think that the fastboot would find the zip file and can unzip and load it just like how it did the testkey one i did before....but i thought i would ask before i tried....maybe i should wait next week until i'm at home and have sd card readers in case anything goes wrong so i can recover the phone easier lol

There is a reason why people don't do that.. When you flash that way via fastboot, it only allow zip files signed by HTC, if you are s-on, and those write everything on the system to stock, which means you lose root and custom/modified recovery.
You could potentially do it that way if you were s-off, but the bootloader flashing utility does not allow as sophisticated commands as the custom recovery does, so everything in the original roms is actually packed in .img files for every partition.

All good advice.
I offered mine as my Desire would not accept CWM 2.5.0.7 (to this day it doesn't), and it would only accept CWM 2.5.1.8 or AmonRa 2.0.1. (as they work on PVT4 with a 40000 page) As for unrevoked, the only version that works for my Desire is 3.2.1, the latest (which I think is 3.3.2) doesn't work on my Desire.
It seems the longer these phones are around, the more individualised rooting and recovery has become, so advice should maybe always come with a word of caution.
***this is what worked for my device***
TinyAggie, I hope you are getting there!

Yep new page size will require the modified cwm for it, but it still has nothing to do with hboot version. However the other recoveries should flash ok as well, they just won't work well for installing roms(gave some error), which he hasn't come to yet

ghalalb said:
All good advice.
I offered mine as my Desire would not accept CWM 2.5.0.7 (to this day it doesn't), and it would only accept CWM 2.5.1.8 or AmonRa 2.0.1. (as they work on PVT4 with a 40000 page) As for unrevoked, the only version that works for my Desire is 3.2.1, the latest (which I think is 3.3.2) doesn't work on my Desire.
It seems the longer these phones are around, the more individualised rooting and recovery has become, so advice should maybe always come with a word of caution.
***this is what worked for my device***
TinyAggie, I hope you are getting there!
Click to expand...
Click to collapse
I found the same thing that only unrevoked 3.2 would work with my device.
I finally managed to flash the custom rom and is what i did to make it all work >_< Maybe it'll help someone else
I started with a fresh official load by flashing the RUU.
Then I used unrevoked that you can download from their website
I still got an error. CID missing. I go searching for it and it seems like a common enough error that the unrevoked team had addressed it
Because of the error, it was not able to unroot and flash recovery properly. The only thing it did was s-off.
So 2 ways to get root/recovery on your phone
1. Manually....find a PB99IMG.ZIP file that has root in it and flash that, then you can either use rom manager to flash the recovery or do it manually as well.
I created my own PB99IMG.zip with the recovery image of clockworkmod for desire using the android info .txt file I had in my other PB99IMG that contained the root access. Put the PB99IMG.zip into your SD card, go to Flash boot and let it do it's magic.
2. Easier way, get unrevoked 3.2 ... There was a warning for using it. Apparently you should only use the 3.2 version if you get the CID error.
But with unrevoked 3.2 it will give you superuser and the recovery image without you doing anything so it's easier.
So after I finally got Root, I backed up my sd card onto my comp.
Then I partitioned my SD card using ROM manager.
Once that was done, i flashed into recovery to do a backup.
After that I tried using ROM manager to flash leedroid...
it looked ok but it never managed to get past the splash screen after 20mins so I pulled the battery and rebooted
Same problem so I decided to flash manually.
Went into recovery and cleared everything then flashed the rom from SD.
Now I'm on leedroid
So far it looks exactly the same as the stock rom. It has everything I need so I'm happy.
I hope this helps anyone with similar problems.
Sometimes you just can't take the easy way out and have to do things manually

[NEED HELP] Hopefully not bricked HTC Incredible with wrong ROM

Guys, please help!! Yesterday I was so hungry for some ice cream sandwich, that I accidentally tried to flash a rom for HTC Incredible S onto my HTC Incredible! Only after the install failed (used Rom Manager, and when it rebooted, it was saying something about missing pb31img.nmh or some weird extension like that) did i realize what i have done. However my phone was pretty much functional at that point. I tried booting into hboot and doing recovery, but whenever i selected any of the hboot options (clear storage, recovery, factory reset), it would just reboot back into hboot. But at this point i was still able to boot into my phone. I tried backing up from saved images using Rom Manager, but when it rebooted, it always gave the pb31img message. Then it just froze. When i pulled the battery and plugged it back in, the phone just got stuck at the HTC Incredible white screen and would not boot. I've been searching the forums long and hard, but it seems all solutions assume i need to be able to boot into the phone, or to be able to simply use hboot to recover. None of these seem to be viable options for me at the moment. Please help with any suggestions as I wanted to wait for the Tegra 3 phones to come out before upgrading!!

fastboot and adb require phone to be able to boot. my phone does not boot into anything besides hboot. and even in hboot, none of the functions work. i was able to format my sd card and copy an img of the proper rom on there, and when i go to hboot->fastboot, it says "loading pb31img.zip" and shows the blue status bar, then says parsing "pb31img.zip" but that takes a second and then it just goes back to the hboot screen without installing anything!! does this mean i'm totally SOL now?

You can use fastboot to flash a stock image. You do not need to be able to boot to use fastboot,fastboot is thru hboot.
http://android-dls.com/wiki/index.php?title=Fastboot#Fastboot_Commands
However if you can get into hboot (the screen with the PB31IMG.zip message), then you can just do an ruu thru hboot. It sounds like your missing or have a corrupt boot image. You need to download the PB31IMG.zip ruu file from here (http://pvillecomp.com/?page_id=22), place it on your sdcard in no folders and then reboot thr phone. Hboot will find the file and prompt you to press vol up to update. Once thats done press vol up to reboot. Your phone should boot now. You will have to reroot if you want.

cmlusco said:
You can use fastboot to flash a stock image. You do not need to be able to boot to use fastboot,fastboot is thru hboot.
However if you can get into hboot (the screen with the PB31IMG.zip message), then you can just do an ruu thru hboot. It sounds like your missing or have a corrupt boot image. You need to download the PB31IMG.zip ruu file from here , place it on your sdcard in no folders and then reboot thr phone. Hboot will find the file and prompt you to press vol up to update. Once thats done press vol up to reboot. Your phone should boot now. You will have to reroot if you want.
Click to expand...
Click to collapse
OMG!!! Thank you soooo much! I can't give you enough thanks, you have no idea! I don't know why this one worked and lots of other cwm img files and rom img files didn't though! And i tried using the fastboot command through the terminal from the computer to flash this same RUU file, but it was giving me problems. But when i put it on the sd card, it worked right away. Now i have a phone to wait out for the Tegra 3!

Glad i could help.

Everything I have read so far says NOT to do any of that through a ROM manager. Could that be why his attempts to install a stock recovery failed?

This really helped me in my situation. I think I had an old version of clockworkmod on my Incredible and it wouldn't let me flash things correctly so it got me stuck in a bootloop but than I flashed the Froyo RUU PB31IMG.zip in hboot and it got my phone working again. Now time to re-root. (I chose Froyo because if you want to re-root with gingerbread you have to downgrade to Froyo which is a hassle)

Your device can not really be bricked. Impossible if you know what you are doing . Revert back to old rom after booting into recovery or choose a simpler from.
Sent from my HTC Incredible S

emaninthenation said:
Now time to re-root. (I chose Froyo because if you want to re-root with gingerbread you have to downgrade to Froyo which is a hassle)
Click to expand...
Click to collapse
If you are s-off it does not matter whether you use the froyo or gingerbread ruu. That is the whole point of getting s-off, so that if an ota or anything else for that matter replaces the custom recovery with the stock recovery, you will still be s-off allowing you to flash the custom recovery right back without having to do all that unrevoked stuff again.

Desire boot loops and I can't get into recovery

I've been happily running CM7 for the past year and yesterday while I was browsing the phone suddenly turned off and starts bootlooping, I then tried to get into recovery to flash one of my backups but I couldn't get into recovery anymore. I can get into the bootloader (vol down, back and power key) but if I select recovery from the menu it starts bootlooping again. I was hoping someone knows what's going on.
I used revolutionary to root the phone, had clockworkmod recovery installed (don't think it was the latest version, haven't updated it since I've installed it a year ago) and was running CM7.2 (latests stable version).
I also apologise in advance because you guys must be sick of people asking what to do with a 'bricked' phone but I'm still hoping someone can help me.

You have the explanation how it all works in my signature.
Just flash recovery.img via fastboot.
Sent from my HTC Desire using Flashes and Thunders

nlooooo said:
You have the explanation how it all works in my signature.
Just flash recovery.img via fastboot.
Sent from my HTC Desire using Flashes and Thunders
Click to expand...
Click to collapse
Thanks for the post, I'm guessing you mean the third link? running the RUU? in that thread there is a link 'http://htcdev.com/' but that link is dead.. so I can't get it there but I will google around to see if it's somewhere else.

the catfishman said:
Thanks for the post, I'm guessing you mean the third link? running the RUU? in that thread there is a link 'http://htcdev.com/' but that link is dead.. so I can't get it there but I will google around to see if it's somewhere else.
Click to expand...
Click to collapse
Not sure what link you said is dead, they all work. I meant on this one "Before Crying for Bricked Device - How Nexus One and HTC Work ".
All you need is recovery.img download it from here:
http://www.clockworkmod.com/rommanager/
and flash it via fastboot.

Both your ROM and recovery are bootlooping. But importantly your bootloader is fine and therefore you can easily recover. First get your recovery in order by flashing recovery from fastboot. Thereafter when you are able to get into recovery flash your ROM in the normal manner or restore your nandroid.

Thank you both! I flashed the recovery.img and could get into the recovery mode again! it's restoring my last back up as we speak, so hopefully it's working again.

If it all work go here:
www.4ext.net
and get rid of that buggy cwm recovery.

Well.. today it started bootlooping again in the same way as described in the first post and now the method I used yesterday to fix it doesn't work anymore. If I flash a new recovery.img now and subsequently try to go into the recovery mode it starts bootlooping again... so now I'm wondering if I should just flash the RUU via pc to at least get my phone working again... do you guys think that would work?
edit: can I even run the RUU in fastboot usb?

RUU is the solution if all else fails. But only use 2.3 Android RUU. And remember to downgrade hboot first.
Before you get into that I would try :-
- Flash a different recovery and try to get into recovery. But this time dont restore your nandroid. Flash a ROM afresh.
- Remove your sdcard and try to get into recovery. Wild guess !
- Also try formatting your system, sdext etc partitions as given in Bortaks thread.

I tried flashing a different recovery (amon ra) but that also didn't work, when I tried to get into recovery mode it got stuck on the HTC boot screen (with some weird extra lines through the image).
I will try to remove the sd card.
Another weird observation, the phone doesn't seem to be charging anymore, at least... the led doesn't turn on when it's plugged in.. it get's weirder and weirder.

like handy says full wipe, wipe/factory reset, wipe dalvik and format all partitions except sdcard then do a clean install of a different rom. restoring the nandroid, u could just be restoring the problem.
edit: just read ur post bout charging, looks like HW not rom or recovery problems
Sent from my HTC Desire

yeah but the weird thing is that this started this morning, I charged it last night (when all of this stuff was already happening).

Run 2.3 ruu as fast as you can, you're on a good way to hboot or radio brick.
:banghead: constuction material guaranteed...
Sent from my HTC Desire using Flashes and Thunders

Well.. the RUU worked, I'm back on sense (ugh).. but at least it's working again.

the catfishman said:
Well.. the RUU worked, I'm back on sense (ugh).. but at least it's working again.
Click to expand...
Click to collapse
You can easily go s-off and root now just go here:
www.revolutionary.io
And the rest is history...
Sent from my HTC Desire using Flashes and Thunders

yeah, I will probably do that in a few weeks, I just moved to another country 2 days ago so I kinda need a functional phone these weeks... aand.. thanks for the help guys

[Q] DHD Stuck on splash screen after trying two ROMs, S-ON, HTCDEV method used.

Hi. I'm aware that this has probably been asked a few times before but I have done some reading and tried a few things but to no avail.
Here's what my phone says in hboot:
***UNLOCKED***
ACE PVT SHIP S-ON RL
HBOOT 2.00.0029
I followed the instructions on HTCDEV (with getting that token and stuff..), then I download Jellytime R11 and Android Revolution, dropped then onto my SD, opened Clockwork Recovery (version 2.5.1.2), wiped everything I should have, installed the zips and both times it hangs on the HTC splash screen.
I used EasyAceRootTool at one stage, where I did that flashing of a boot.img.
While installing in CWR I don't get any error messages, and with Revolution, I went through the GUI fine (where you choose which apps to install etc.)
It's just when I go to reboot, it hangs.
Not sure if it's relevant, but I'm on T-Mobile UK.
Thanks in advance for your help guys, I'd love to get this sorted, I've only just been given this phone.

Each time you flash a ROM, you need to flash the boot.img.

bananagranola said:
Each time you flash a ROM, you need to flash the boot.img.
Click to expand...
Click to collapse
I think my problem is this.
When I wipe everything and install the ROM, I can't get back into HBOOT, I'm stuck in CWM, I go to Advanced -> Recovery Boot and it stays in CWM, I go to Go Back and it stays in CWM.. The only way I can get back to HBOOT (to get into fastboot) is to take the battery out, which I'm guessing then messes up the ROM I've just flashed.

I've just it in perfect order, so installed zip then flashed the boot.img and I'm still stuck on the splash screen. It's been ten minutes now.

What exact process are you using?

I've just done it!
I had an old version of CWM on my sdcard from a previous flash on a different phone. I thought it would have updated it (I'm sure it said it did..) but I just manually did so and then it had a different skin and I went through the process again and it worked.