This is what happened:
I received a used Alltel PPC6800. It had WM5 installed. I called Alltel to activate the phone. It activated and reset itself... to the bootloader. I couldn't get it out of the bootloader, so I thought what the hell, I'll upgrade to the latest ROM that HTC put out for the Alltel PPC 6800.
The ROM loaded fine, and upgraded to bootloader to SPL-2.07.. However, it was stuck in the bootloader. So, I did a soft reset. Windows 6 started up. Then it went to auto-install the Alltel custom software. Then it reset, and has been stuck in the bootloader screen ever since. It can't be hard reset, it can't be soft reset... reloading the ROM doesn't work. I can't try changing bootloader versions because I need to be in the OS to do that. I can't load an older ROM, because it won't let me do so... it fails at 1% and says something about an Invalid ROM.
Oh, and that titan_exitbl.exe program doesn't work. It just resets the phone back to the bootloader.
I will be mailing it out for an exchange in the morning unless someone here may know of a way to get it working again.
Thanks!
NO its not bricked, it wouldnt power on. Sounds like its messed up good though, good luck
Well, I found that I *could* get it to load the OS if I used MTTY and the 'set 0 16', 'boot' trick.
I then upgraded the bootloader to above 2.4. However... it still hangs at the bootloader screen if I reset the device.
So... It seems something else is going on, that is preventing the device from loading the OS on it's own. I can't really be plugging it into a computer and running MTTY every time I need to reset the damn thing.
Any ideas?
mantispid said:
Well, I found that I *could* get it to load the OS if I used MTTY and the 'set 0 16', 'boot' trick.
I then upgraded the bootloader to above 2.4. However... it still hangs at the bootloader screen if I reset the device.
So... It seems something else is going on, that is preventing the device from loading the OS on it's own. I can't really be plugging it into a computer and running MTTY every time I need to reset the damn thing.
Any ideas?
Click to expand...
Click to collapse
Have you tried to flash since you upgraded the BL....if not give it a shot and see what happens....use the SD method to flash....put NBH file on card and rename it to TITAIMG.nbh
Yup, just tried flashing from microSD, and it flashed just fine, but has the same problem.
It won't exit the bootloader. I wish I had a USB headset adapter to see if that would make it boot. I've heard that works for some of these that have this problem.
Related
i was originally in a 3.16 gps rom, but decided to use dcd 2.3.1 instead.
So after flashing the rom and getting stuck at tri-color screens and such. I used cokeman's tool to get out of the bootloader screen.
the weird thing is that whiel trying to flash the rom, the instructions said make sure i have an activesync connection, i couldn't get a connection even after unplugging and plugging it in. i just went ahead and clicked next.
everything seemed fine but when i unplugged the usb from my phone to my laptop, and when i was about to leave. the titan started resetting itself on its own after about 5 seconds from restarting.
help!!!!
i managed to flash the rom to a dcd 2.3.1, but the problem continues. it'll restart everytime and will only stop when its plugged into the computer. has anyone ever experienced this?! i really need help
Hmm, this seems nothing like the 30 or so other threads about phones resetting.
ive tried a search, but did not find any threads on this matter. any help?
zerogravity said:
ive tried a search, but did not find any threads on this matter. any help?
Click to expand...
Click to collapse
Lol somehow I doubt that, but I might be wrong. What version unlocker do you have?
limezednem said:
Lol somehow I doubt that, but I might be wrong. What version unlocker do you have?
Click to expand...
Click to collapse
http://forum.ppcgeeks.com/showthread.php?t=9093
from there
And just to make sure, when you press Power + Camera + Reset, it says Olipro 2.40
Also you are completely sure you have Radio 3.27 and a current DCD's rom.
Radio can be verified by soft reset and bottom left should say
R 3.27.00
D 3.16
reflash dcd rom
The Problem Is...
Every time i restart my phone via any type of reset....
(soft reset, hard reset, battery out of the phone, powerbutton turn off, a programs phone restart)
... the phone turns straight to the bootloader screen. It does not do the normal viberate and restart.
To get the phone to restart I have to go through a long process of removing the battery, plugging it into the charger, pressing all the buttons with a million resets.
Then eventually it will start up like normal.
Titan_exitbl.exe does not do anything... It sends the code and goes straight back to bootloader screen with any of the bootloaders stock or olipro customs
What I Have Tried:
installing and reinstalling the 3.39, 3.35, 1.30 stock radio
installing and reinstalling correct combinations of roms for the above radios. (including stock)
installing all bootloaders (including relocking)
each with their corresponding roms and radios
What I Think
Because of not being able to hard reset something is wrong there.
i'm open to suggestions
Where exactly are you right now?
What bootloader, ROM, and radio do you have installed? Are you able to boot into Windows Mobile?
right now completely stock i'm in windows mobile
i have now done a hard reset via settings->system-> clear storage
EDIT more exactly
verizon rom 2.09
radio 1.30.60
bootloader 1.06
Ok...do you have a microsd card to flash with?
not right now however,
let me know what you're thinking i might go grab one.!
I've got the same thing happening to me... I was running the test "sprint" radio on my alltel 6800 along with no2chem's latest rom... it started happening, so I decided to install the newest stock alltel rom... didn't fix it at all. What sucks now is I can't even get activesync working witht eh alltel rom now...
Also, I can get it to boot if I do one thing. If I connect up a usb cord (to a computer, or my usb headphone adapter) and hit soft reset, it'll boot fine.
However, soon as I hit that soft reset button on the bottom again, back to bootloader it goes.
This happened to me once before a long time ago, I fixed it by relocking the device and installing a stock Alltel rom... however I've read that's a bad idea with the newer GPS enabled roms and can kill the phone.
any ideas?
Just a quick update... after messing around I had an idea... I connected the USB headphones so I could actually do a soft reset that works... But this time, instead I held down the power/cam when I did it so it would load the boot loader... my thinking was that it might trick it into not loading it. Sure enough, it worked. Now when I hit soft reset, it does just that. No more boot loader unless I hold down those buttons.
Very strange... like the phone got tricked into thinking the buttons were always pressed down on restart.
Anyways, hopefully this will help others that might come across this issue.
spoke too soon... now its is doing it again after flashing the sprint rom back on and then no2chem's latest.
argh...
My phone was working fine for sometime with DCD 3.1.2, SPL 2.40 and radio 3.39.10. Last week it starting randomly resetting when I would slide open the keyboard. Not always, but quite annoying. The past few days it started getting stuck in the bootloader on initial start. I would reset it, remove the battery, etc. Still it would go to the bootloader. I even tried the exitbl utility and although it sends the data and executes the reset, it still goes back to the bootloader. Screen says:
TITA100 MFG
SPL-2.40.Olipro
CPLD-9
I figured it was a bug with the rom or whatnot, so I (microsd) reflashed it with the latest official Sprint rom. It still goes into the bootloader. If I hit the reset button enough times, it will occasionally boot up. No idea what's goin on here. Don't understand how it could be random either.
Any ideas?
do you have the wire that you plug in for headphones?
it's the headphone/ USB plug?
if so plug it in and just push the soft reset button
it should work
Ok, that worked like a charm, thanks!
Question is it still enters the bootloader when I reset or turn off/on the phone without the adapter. Should I reflash the bootloader?
i have found no info pointing towards what is doing it. i've re-flashed with no luck
Is there a way to flash the bootloader off just the memory card? Can I copy the Hard_MFG_SPL_2.40_RUU_signed.nbh file to a card and rename it?
Figure it's worth a try.
I've got the exact same situation as you guys... Just wanted to chime in on it.
cpujunky said:
Is there a way to flash the bootloader off just the memory card? Can I copy the Hard_MFG_SPL_2.40_RUU_signed.nbh file to a card and rename it?
Figure it's worth a try.
Click to expand...
Click to collapse
i think i read on another forum that you can not flash off the memory card for a bootloader.. but i do not know
Try a hard-reset and then flash to another pre-built or Kitchen built ROM that uses the 2.40 bootloader.
You must boot into the WinMo OS and get connected with Activesynch to program a bootloader. At least none of us have yet managed to figure another way to do it.
Is there a way to flash the bootloader off just the memory card? Can I copy the Hard_MFG_SPL_2.40_RUU_signed.nbh file to a card and rename it?
Figure it's worth a try.
Click to expand...
Click to collapse
Do NOT, I repeat do NOT attempt to update the SPL with the memory card. The unlockers are developed to first load a temporary bootloader, then flash with an RUU once using the temporary. You will mess up your phone.
Thanks... I was having the same problem that the OP was having until I found this thread. It seems like headphone adapters other than the Sprint one works. Also, if you're stuck in the bootloader, there is no reason to flash any roms because it will have no effect at all.
Also, as an alternative, you can take out the battery for a couple hours.
By the way, I'm running dcd 3.1.2 and radio 3.37
So we know that flashing a new ROM doesn't work, and flashing different radios doesn't work. We also know the headphone adapter will get you to boot up normally, so no stuck buttons or anything. This has to be a bootloader bug or phone defect or bent usb pins or something. Has anyone tried relocking the phone? I can't express how annoying it is to carry around a headphone adapter in case you need to reboot.
Thinking,,,,,
I stopped where you see in my signature as everything works for me, but I wonder if maybe you flash back to stock, relock, put it back exactly as you started if that would straighten it out. If it still fails stock then some nice new defect has been found. If it works then go forward but only as far as I did ans see if it is stable as with mine,,,,,maybe somthing in the new ROMs???????
cpujunky said:
So we know that flashing a new ROM doesn't work, and flashing different radios doesn't work. We also know the headphone adapter will get you to boot up normally, so no stuck buttons or anything. This has to be a bootloader bug or phone defect or bent usb pins or something. Has anyone tried relocking the phone? I can't express how annoying it is to carry around a headphone adapter in case you need to reboot.
Click to expand...
Click to collapse
i have relocked also. i've think i've done everything except rip the phone apart and look at the usb pins
This is not a rom issue, it's a bootloader issue. I've flashed, tested, and used all released roms and non-released (internally tested) roms numerous times on several different titans and have never seen this issue. I'm not doubting the existence of the issue, but the rom will have nothing to do with the device being stuck in the bootloader.
My guess is that something went wrong while unlocking or it's a hardware defect on a certain batch of these phones.
there was some talk over at ppcgeeks about there being something about relocking and flashing and something... however. my phone worked great and then one day it just started and nothing changed on the phone for like 3-4 weeks and then it started going to bootloader
This weekend I replaced the stock bootloader on my VZW XV6800 with SPL-2.40.Olipro; upgraded radio to 3.39.10; installed dcd's Titan 3.1.2. All went well, phone was doing fine for a couple days.
Today the battery died, nothing unusual. I plugged in AC power and turned on the phone and the bootloader displayed. Did a soft reset 2 or 3 times, no change. Disconnected AC, popped out the battery, let it sit while I search and found this thread.
I used a can o' air to blast out the USB/power port on the phone. Put in the battery, powered the phone, and the OS loaded just fine. Soft reset the phone and again could only get to the bootloader. Poppped out the battery again, found my USB/headphone adapter, connected it, returned the battery and powered the phone, and the OS loaded just fine.
This is a long way of saying I'm experiencing the same that's been reported in this thread. Is there a fix for this issue? It seems like an issue with the device to me. Was there any confirmation that there was a "bad batch" of phones and is a hardware issue with the XV6800?
I am also experiencing this same problem.
I flashed to 3.1.2, then to 3.2.0 today...nothing changed. It still loads the bootloader when i do any kind of a reset without the usb or the headphones plugged in.
The only odd thing that i can comment on during my experience is that my USB cable failed on me and I had to replace it. Seems odd, but perhaps that can shed some light on the problem.
Did anyone find a solution to this problem? Is it a hardware issue?
the weirdest thing started happening today. i was using my phone as normal this morning (i had soft reset 1 or 2 times earlier) and all of the sudden when i soft reset on psShutXP, it took me into bootloader. odd, but nothing an old exit_BL couldnt fix. well it wouldnt send the commands, but i found out later that once i connect the USB to my computer and it beeps, i can soft reset out of BL. but now its happening EVERY time i soft reset, even running Sprite Backup, when it soft resets, it puts itself into BL. i was running DCD 3.2.2 and i reflashed a clean ROM (and also 3.2.3) and the problem is still arising. im thinking its hardware, but i havent dropped it or got it wet. any ideas?
alright so now im completely stuck in bootloader, it wont even do anything. i left the battery out last night and it booted fine this morning. however as soon as it reset after UC (it hard reset itself) it went back into bootloader. i was trying to load the stock radio/rom so i can just take it in but it wont connect to activesync at the tap to begin. i need some serious help.
have you tried a hard reset from bootloader? you were a little confusing in your posts. what exactly are you doing from boot time to ending in BL? are you able to reflash, then after UC you get stuck in bootloader? are you doing a full restore with Sprite Backup? can you clarify exactly what is going on, step by step?
it wont hard reset in bootloader. it just refreshs the screen. well since i am in bootloader, yes, i can flash. i flashed and after it boots and runs UC and loads the programs, it soft resets and goes into bootloader. the only way i can get out of bootloader is to plug in the USB, wait a minute, then soft reset. if i soft reset (either manually, Sprite, or psShutXP) it goes into bootloader. im not 'stuck' in bootloader because i can get out, and exitBL still does nothing. ive been trying to brick it but nothing is working.
have you tried flashing and booting with your SD card removed so UC doesnt run?
kflipproductions said:
have you tried flashing and booting with your SD card removed so UC doesnt run?
Click to expand...
Click to collapse
yep, and cooked a clean ROM with UC unchecked. ive never seen anything like this, its bizarre.
so even with UC off, no SD card, after reflashing if you soft reset it loads BL?
kflipproductions said:
so even with UC off, no SD card, after reflashing if you soft reset it loads BL?
Click to expand...
Click to collapse
yes. im pretty much at a dead end for ideas.
have you tried reflashing bootloader itself? or a different version?
nope, trying it now.
let me know..
nope still doesnt do anything. still soft resets into bootloader.
damn. thats weird. have you tried relocking it?
kflipproductions said:
damn. thats weird. have you tried relocking it?
Click to expand...
Click to collapse
i cant; it wont connect to activesync even on the today screen or anywhere. but the computer does beep so i know its connected.
get back to the point where you can boot to the today screen and turn 'advanced network functionality' off before you connect to activesync.
edit: nevermind, its not doing anything. im at the today screen. it started connecting but nothing happened.
alright thank you i got it back to stock but im going on a surfing trip til sunday so ill see what i cant do when i get back. thanks a ton
-Nick
what did you end up doing?
i took out the battery for 10 minutes and it booted up, and after being USB connected to the computer for another 10 minutes, activesync started. i flashed the stock radio/ROM and relocked to the 1.06 bootloader because i cant find the stock 1.04. anyone know if its possible to flash the 1.04 bootloader?
im thinking i could just play dumb when they ask about it. Something along the lines of, "Ohh, thats just how it came. Flash? Whats a ROM? Bootloader? HUH?"
There is no 1.04 bootloader. It comes stock with the phone. Having 1.06 on there will be fine trust me.
I think I may have bricked my OG HD2 (T8585) while trying to undo everything I had done to it, which was HSPL, MAGLDR and a NAND Android ROM.
It all started when I first tried to flash Kingdom's Sense 3.0 Gingerbread ROM. It told me to create a 340MB partition using HD2 Toolkit which I did. I then flashed the ROM as per the instructions, but it kept getting stuck on the boot logo so I decided to go back all the way to stock WinMo.
I downloaded a stock 1.66 ROM from HTC's website, tried to flash it via USB which failed because I obviously have no ActiveSync in Android. So I loaded the image onto my SD card and tried to flash by holding Vol Down and Power.
That was the first sign of trouble, about 1/10th during upgrade process it gave me some errors and rebooted to a black screen with a silver warning triangle.
Trying to go back into bootloader, I got the message about "upgrade ROM code error."
Since it had reverted back to SPL 1.42 I tried to reflash HSPL2 through USB, which worked fine, got the "We bricked it " message and everything. But then I tried to install MAGLDR and nothing, it fails even though it recognizes the USB connection.
So what can I do? On the one hand my device can accept and load HSPL2 and my computer is recogonizing the USB connection, but other than that nothing, it won't even turn on without being connected to external or USB power.
I also tried installing stock 1.43 ROM and that goes fine, it gives me an okay on everything but it gets stuck in the white HTC bootscreen in a loop.
I know I probably made a huge glaring mistaking to cause this, it's probably because I've bought a Transformer tablet and a Galaxy S2 in the last month so the steps regarding the HD2 were probably a bit of a blur. I guess the stock ROM probably included a radio that I wasn't supposed to flash, causing my device to be bricked.
But is there anyway I can get some type of OS working on this poor HD2 now?
She lives!!!
Okay, I'm not actually sure if the problem is solved but I'm back in WinMo 6.5 for the time being.
Since it had been off for a few hours I tried my luck again, plugged it into the wall and saw that it was stuck in the boot loop again. But I got distracted and left it, and when I came back it was on the orange WinMo setup screen.
Not sure what happened to make it go from not even getting power from the battery to working normally. But I see now my radio version is 2.05 which is massively old, I'm going to try and upgrade that first and see... hopefully it won't go back to being dead the moment I power down.
Shawn_230 said:
I think I may have bricked my OG HD2 (T8585) while trying to undo everything I had done to it, which was HSPL, MAGLDR and a NAND Android ROM.
It all started when I first tried to flash Kingdom's Sense 3.0 Gingerbread ROM. It told me to create a 340MB partition using HD2 Toolkit which I did. I then flashed the ROM as per the instructions, but it kept getting stuck on the boot logo so I decided to go back all the way to stock WinMo.
I downloaded a stock 1.66 ROM from HTC's website, tried to flash it via USB which failed because I obviously have no ActiveSync in Android. So I loaded the image onto my SD card and tried to flash by holding Vol Down and Power.
That was the first sign of trouble, about 1/10th during upgrade process it gave me some errors and rebooted to a black screen with a silver warning triangle.
Trying to go back into bootloader, I got the message about "upgrade ROM code error."
Since it had reverted back to SPL 1.42 I tried to reflash HSPL2 through USB, which worked fine, got the "We bricked it " message and everything. But then I tried to install MAGLDR and nothing, it fails even though it recognizes the USB connection.
So what can I do? On the one hand my device can accept and load HSPL2 and my computer is recogonizing the USB connection, but other than that nothing, it won't even turn on without being connected to external or USB power.
I also tried installing stock 1.43 ROM and that goes fine, it gives me an okay on everything but it gets stuck in the white HTC bootscreen in a loop.
I know I probably made a huge glaring mistaking to cause this, it's probably because I've bought a Transformer tablet and a Galaxy S2 in the last month so the steps regarding the HD2 were probably a bit of a blur. I guess the stock ROM probably included a radio that I wasn't supposed to flash, causing my device to be bricked.
But is there anyway I can get some type of OS working on this poor HD2 now?
Click to expand...
Click to collapse
I had pretty much the same problem as you, but mine is the tmobile us version. I tried flashing back winmo from android via sdcard method but i got an upgrade error. I tried flashing with microSD card sizes 8gb, 16,gb, and then 2gb which was recommended, but still no luck. I managed to connect the hd2 through usb on the tricolor screen and flashed back to hspl2.08 and magldr and cwm were still on. But i would like to still get back to winmo stock as if it came from tmobile.
My question is if i download the latest update from tmobile which is T-Mobile HD2 MR Software (Version 3.14.531.1), what is the correct spl i should have installed on the hd2 so that htc and tmobile wont know that i messed with the spl? is it 3.03? I was going to connect via USB on the tri color screen again, run the EXE and manually install the SPL? I just need to know which SPL to install after i run the latest winmo update. Please advise on the SPL and the method i'm going to take on reverting back to winmo. Thanks.
germotlp said:
I had pretty much the same problem as you, but mine is the tmobile us version. I tried flashing back winmo from android via sdcard method but i got an upgrade error. I tried flashing with microSD card sizes 8gb, 16,gb, and then 2gb which was recommended, but still no luck. I managed to connect the hd2 through usb on the tricolor screen and flashed back to hspl2.08 and magldr and cwm were still on. But i would like to still get back to winmo stock as if it came from tmobile.
My question is if i download the latest update from tmobile which is T-Mobile HD2 MR Software (Version 3.14.531.1), what is the correct spl i should have installed on the hd2 so that htc and tmobile wont know that i messed with the spl? is it 3.03? I was going to connect via USB on the tri color screen again, run the EXE and manually install the SPL? I just need to know which SPL to install after i run the latest winmo update. Please advise on the SPL and the method i'm going to take on reverting back to winmo. Thanks.
Click to expand...
Click to collapse
So it sounds like you lucked out, huh? So your HD2 works at least? I believe if you succesfully flash an official ROM like from T-Mobile, it will replace everything including the SPL back to stock - this is what I was trying to do by flashing official 1.43, to go back to factory mode.
I seem to be worse off than you though. I posted last night how my HD2 was back up running WinMo, but as suspected the moment I rebooted it was back stuck in the boot loop.
Any ideas? I wish I could get the HD2 working again so I could set it aside and get to playing with my new Galaxy S2.
This is driving me crazy now...
I managed to flash HSPL 2.08, and then MAGLDR 1.3, and then CWM recovery on top.
But this still seems bricked to me, still needs external power to turn on and I can't actually flash a working ROM... flashing a ROM via USB gives connection error and flashing via SD card goes fine but gets stuck in a boot loop.
What can I do at this point short of tossing the phone? I've tried stock 1.48, stock 1.66, a bunch of radios from 2.05 to 2.15... everything.
I am doing some research but the only results I find are T-Mo HD2s being bricked by the wrong radio. I have an original HD2 and I never flashed a radio intended for another HD2 model, so how is my phone so bricked all of a sudden?
All the threads I've found say if you can get into the bootloader then there's some hope but I doubt it because I can't successfully flash anything with it. I don't even know how I managed to get back into WinMo briefly last night... think my HD2 is probably just toast.
Okay, I finally solved my problems for sure - bent charging leads in the battery compartment!
Anyone having boot issues, take out your battery and look at the metal leads and you will probably find them bent out of shape. They are incredibly flexible, so just make them straight again and it will work. I assume it cuts external power briefly right before booting into WinMo, which is why it was rebooting constantly.
So I suppose for me this was a huge case of confusion, I got all confused with bootloaders and MAGLDRs when the problem wasn't even software related.
Shawn_230 said:
So it sounds like you lucked out, huh? So your HD2 works at least? I believe if you succesfully flash an official ROM like from T-Mobile, it will replace everything including the SPL back to stock - this is what I was trying to do by flashing official 1.43, to go back to factory mode.
I seem to be worse off than you though. I posted last night how my HD2 was back up running WinMo, but as suspected the moment I rebooted it was back stuck in the boot loop.
Any ideas? I wish I could get the HD2 working again so I could set it aside and get to playing with my new Galaxy S2.
Click to expand...
Click to collapse
The problem with my hd2 is the CPU is overheating thus causing it to freeze or lock up, and gets it annoying. After hours of searching on XDA, that's what seems to be the problem. I can't even talk on the phone for more than ten minutes or else locks up. So my idea was to get it back to winmo stock and see if it still locks up. If it does then i will probably try to send it back to HTC and see if they send another one maybe or fix it.
Ive had no luck luck flashing back to winmo from sdcard so i think i should try flashing back to winmo via usb on the tri color screen. Ive read on XDA that if you flash winmo via usb that it doesn't replace your SPL, and you have to run HSPL4 and flash it manually. I'm just not sure which SPL i should flash. I'm assuming 3.03 maybe?
What you could try is using an sdcard that is 2gb or less. Ive read that anything higher than 2gb will cause issues. I'm still a noobie at this rooting biz. Hope that helps.
germotlp said:
The problem with my hd2 is the CPU is overheating thus causing it to freeze or lock up, and gets it annoying. After hours of searching on XDA, that's what seems to be the problem. I can't even talk on the phone for more than ten minutes or else locks up. So my idea was to get it back to winmo stock and see if it still locks up. If it does then i will probably try to send it back to HTC and see if they send another one maybe or fix it.
Ive had no luck luck flashing back to winmo from sdcard so i think i should try flashing back to winmo via usb on the tri color screen. Ive read on XDA that if you flash winmo via usb that it doesn't replace your SPL, and you have to run HSPL4 and flash it manually. I'm just not sure which SPL i should flash. I'm assuming 3.03 maybe?
What you could try is using an sdcard that is 2gb or less. Ive read that anything higher than 2gb will cause issues. I'm still a noobie at this rooting biz. Hope that helps.
Click to expand...
Click to collapse
Which model HD2 do you have?
Find and download the stock ROM from this thread, get 1.66 since it will work with HSPL2 which is the latest HSPL that will work with MAGLDR (for Android and WinPhone7).
You can flash that through SD card and it will go back to total stock, including stock SPL. I assume you know how to pull the .nbh file from the ROM you download, so just rename to LEOIMG.nbh and put it on your SD card.
Go into the tri-color screen and it should flash fine and give you factory reset. This is where it wasn't working for me, but not because I had flashed the wrong ROM or something but because I had messed up the charging leads in the back while popping the battery in and out to reboot as I was flashing.
Man I downloaded 1.66 last nite and tried to flash back to winmo from android and its toast. Not sure what went wrong. Oh well.
Sent from my HTC Sensation 4G using XDA App