Related
I had heaps of problems before, I just reflashed the original ROM and all was working well again, The radio version that come with the ROM is old.
Then I followed this guide
And updated to Hard-SPL v7 fine
Then I got to the Radio update step, I tried the radio it said (1.43)
It got to 7% and failed,
Then I tried 1.48 and 1.50
The same happened.
Why can't I update my Radio? Is there a trick or something you guys use?/
I tried it the SD card way and Its the Same.
Thanks.
Can a pro please explain how and what they used to get their PDA from its original state to having a cooked OS and a working Radio?
Korpse said:
I had heaps of problems before, I just reflashed the original ROM and all was working well again, The radio version that come with the ROM is old.
Then I followed this guide
And updated to Hard-SPL v7 fine
Then I got to the Radio update step, I tried the radio it said (1.43)
It got to 7% and failed,
Then I tried 1.48 and 1.50
The same happened.
Why can't I update my Radio? Is there a trick or something you guys use?/
I tried it the SD card way and Its the Same.
Thanks.
Can a pro please explain how and what they used to get their PDA from its original state to having a cooked OS and a working Radio?
Click to expand...
Click to collapse
That guide works 99% of the time. There is really only a small handful of possibilities:
1) You did not follow the guide exactly
2) The file you got for radio is corrupt (unlikely since you tried multiple files)
3) Your connection is unstable (unlikely since SD card method fails)
Hmm... Try the bricked hermes thread - is a sticky in the Hermes forum. It is long, but you may find something. It seems to me that the 7% hang on radio happens from time to time - but I am not sure if there is a standard fix. Maybe try the google search in my signature - use terms like hermes radio 7% brick or something. I am sure it is fixable. You got HardSPL to load properly, right? So your bootloader screen shows SPL version 2.10 Olipro or something like that?
The interesting thing is that you got it back to oringinal ROM & radio... You are using the latest Custom_RUU to do all the work. Makes me wonder if it is a CID problem, although I don't think you would even get to 7%, you would just get an immediate failure.
You could use MTTY to restore the radio back to factory I beleive..
You might also need to make sure your device is CID unlocked..
Thanks for the help guys
I updated to HardSPL-v7 and that went fine, it read IPL-1.04 and SPL-2.10.Olipro afterwards,
Then I attempted to update the radio and it failed, I followed the guide exactly.
Then I tried the SD way, the same.
Now. I'm doing the SIM and CID unlocker v3a by pof (Did it the SD way) and the IPL update completed with OK, The SPL went OK to, but the radio failed so i did a reset now I going to run that unlocker program and see if it succeeds,
then I will run the Factory ROM and restore it to how it was, then I will update to the Black Satin Cooked ROM, and I'll just have to stick with the old radio until I find a new method that might work.
Whats the go with the downgrading to bootloader 1.04 like it says in the wiki everywhere, what will that do that will help the radio update that the newest bootloader can't?
Korpse said:
Thanks for the help guys
I updated to HardSPL-v7 and that went fine, it read IPL-1.04 and SPL-2.10.Olipro afterwards,
Then I attempted to update the radio and it failed, I followed the guide exactly.
Then I tried the SD way, the same.
Now. I'm doing the SIM and CID unlocker v3a by pof (Did it the SD way) and the IPL update completed with OK, The SPL went OK to, but the radio failed so i did a reset now I going to run that unlocker program and see if it succeeds,
then I will run the Factory ROM and restore it to how it was, then I will update to the Black Satin Cooked ROM, and I'll just have to stick with the old radio until I find a new method that might work.
Whats the go with the downgrading to bootloader 1.04 like it says in the wiki everywhere, what will that do that will help the radio update that the newest bootloader can't?
Click to expand...
Click to collapse
If the CID unlocker runs fine, try the radio again. There is no reason that a new one would not work, if the older one works routinely.
The downgrade stuff is for people who want to return it to it's near-exact shipped condition - usually for warranty or sale purposes.
So, I ran the original factory rom
I did it via the SD card, as it is a lot more useful this way.
Heres the Results:
IPL - OK
BOOTLOADER - OK
SPLASH1 - OK
SPLASH2 - OK
EXTROM - OK
GSM -
OS-
Click to expand...
Click to collapse
please mind the ranting....
WTF WHY THE F##K DID IT STOP AT GSM AGAIN FFS!
you can obviosly see why I'm pissed, its acting up like the radio is a BANK VAULT with 8" STEEL. I just can't flash it at all, but for some reason I have ran this ROM a while back and had no problems, so there must be a way
Did you run the CID unlocker successfully?
Have you used MTTY before? You may want to do that.
Had you successfully flashed back to the old ROM before?
I had heaps of problems before, I just reflashed the original ROM and all was working well again, The radio version that come with the ROM is old.
Click to expand...
Click to collapse
It seems like it - so the SAME ROM will not work now either?
I ran the newest dopod wm6 rom which was only the OS, some splash screens and the EXTROM, and to my amazement the GSM worked, the Radio and IMEI reappeared in the device information, but after a soft reset its gone again. it seems the GSM is still there but I can't touch it at all.
When I did the SIM and SuperCID unlocker it gets to the hacked GSM and fails,
but after a reset, I ran the tool and ticked bot options. then it said Success!
How can I check to see if it worked.
My bootloader is 1.40.Olipro (the one the SIM and CID unlocker downgraded me to)
Korpse said:
I ran the newest dopod wm6 rom which was only the OS, some splash screens and the EXTROM, and to my amazement the GSM worked, the Radio and IMEI reappeared in the device information, but after a soft reset its gone again. it seems the GSM is still there but I can't touch it at all.
When I did the SIM and SuperCID unlocker it gets to the hacked GSM and fails,
but after a reset, I ran the tool and ticked bot options. then it said Success!
How can I check to see if it worked.
My bootloader is 1.40.Olipro (the one the SIM and CID unlocker downgraded me to)
Click to expand...
Click to collapse
You can use mtty to see if the supercid process worked. The Hermes Wiki - in particular THIS SECION will be very helpful.
Yep its definitely SuperCID,
still reading through pages looking
I spent HOURS messing with **** on my phone, downgrading bootloaders, trying different ROMs, Stuffing with every command I could find for MTTY and anything else imaginable.
I got the radio to update, but its still stuffed
I added this to the Wiki because it works:
METHOD 2
Also, Ive found that Hard-Reseting the device restores GSM.
1. Remove the battery
2. wait 10 second
3. Re-insert Battery
4. Turn the device on
5. Watch for "NO GSM" on boot
6. if you see it. Return to step 1. (sometimes you have to do it up to 20 times)
If you see two lines of text flash up instead of 'No GSM' it means the GSM is functioning. For me this restored my radio in just 4 tries.
This ONLY works if your radio is NOT corrupted, but if you tried to updgrade and stalled between 0% and 15% of the GSM upgrade, it depends on the radio version you were trying to flash. But it's worth a try, the only downside is if your phone crashes, it will more than likely boot up with 'No GSM' so you'll have to do all over again.
Click to expand...
Click to collapse
I did what the last post said, had it booted with my radio working, and then I ran the RUU for the GSM 1.50.00.00 radio upgrade. and THIS IS UNBELIEVEABLE, AFTER ALL THAT STUPID STALLING ON 0 and 7%, it UPGRADED!!!!!
I have exactly teh same situation here.... my device is SUPERCID and its stalls on GSM upgrade every time
I already tried like 10 different versions of radio bootloader updates and none of them worked for me !!! It always stalls at 11% or 7%
MMTY output
Cmd>checkimage
IPL CRC checksum = 0x830E7601
SPL CRC checksum = 0x921BC30
CE CRC checksum = 0x26BC961C
ExtROM CRC checksum = 0xE7056FB7
Radio Image CRC checksum = Checksum: Wait interpreter timeout
0x0
Can somebody help ? I am sure there is a way to flash the new radio version !!!
There is a defenitite fault in RADIO ROM and I wish I should have never tried to upgrade to 1.50.0 . Last coule of days have been a nightmare for me. I read the entire foruma and stil could not find a solution to my problem.
METHOD 2
Also, Ive found that Hard-Reseting the device restores GSM.
1. Remove the battery
2. wait 10 second
3. Re-insert Battery
4. Turn the device on
5. Watch for "NO GSM" on boot
6. if you see it. Return to step 1. (sometimes you have to do it up to 20 times)
If you see two lines of text flash up instead of 'No GSM' it means the GSM is functioning. For me this restored my radio in just 4 tries.
This ONLY works if your radio is NOT corrupted, but if you tried to updgrade and stalled between 0% and 15% of the GSM upgrade, it depends on the radio version you were trying to flash. But it's worth a try, the only downside is if your phone crashes, it will more than likely boot up with 'No GSM' so you'll have to do all over again.
Click to expand...
Click to collapse
sure i've done it too many times, atleast after the 7nth time i've stopped counting but still i have no GSM .
any help is much appreciated folks .
WBR
Also whatever ROM i install after it starts for the first time it starts to customize and install oem apps it stops while customizing at the theme part i don't know why but it did .
do a "checkimage" in MTTY, if your radio is corrupt then that method wont work, also about the updates stalling, do task 28 in MTTY, then reboot
MMTY output
Cmd>checkimage
IPL CRC checksum = 0x830E7601
SPL CRC checksum = 0x921BC30
CE CRC checksum = 0x26BC961C
ExtROM CRC checksum = 0xE7056FB7
Radio Image CRC checksum = Checksum: Wait interpreter timeout
0x0
So is the radio corrupt ?
What is task 28 ? WIKI SAYS - Format DOC - What is DOC ? Is it related to RADIO ROM ?
After flashing my locked T-mob vario dutch (for the 20st time) it now is bricked.
I tried to flash the Fun_Key_rom.
Hermes is stuck on the HTC logo 1pl-1.01 and SPL-2.03 not Super CID. (because of the warranty). I followed the thread about unbricking, but untill now no result.
I can flash it with Ruu.exe (and ruuwrapper.exe) the option 2.02/2.10 works for me untill 1% and then I get a invallid vendor ID.
I read the thread over and over again, but didn't seem to get how to unbrick it. Do I need to have a special rom? or other software?
no you need to flash Hard SPL on your phone right now!!! you can always unflash the HardSPL at a later date but you where just asking for a brick by not flashing HardSPL in the first place!
austinsnyc said:
no you need to flash Hard SPL on your phone right now!!! you can always unflash the HardSPL at a later date but you where just asking for a brick by not flashing HardSPL in the first place!
Click to expand...
Click to collapse
Had no problems for all those times..untill now I know it was stupid.
Trying to flash Hard SPL I got a 260 update error on the HardSPL v7. I also tried it with another upgrader and got an 270 error. It installed until 100% but no result.
marcoryn said:
Had no problems for all those times..untill now I know it was stupid.
Trying to flash Hard SPL I got a 260 update error on the HardSPL v7. I also tried it with another upgrader and got an 270 error. It installed until 100% but no result.
Click to expand...
Click to collapse
Yes, you need to use CustomRUU to avoid the invalid vendor ID. It bypasses the CID check. That is why it works, even though you are not superCID.
Regarding the 260 error, try a couple things.
If you can, try SD flashing.
If you cannot do SD method, try using "manual bootloader" method:
- Put phone in bootloader mode
- NOW attach to USB lead
- Start CustomRUU
If that does not work, try taking the battery out for a while (5 minutes) and then try again.
todd_jg said:
Yes, you need to use CustomRUU to avoid the invalid vendor ID. It bypasses the CID check. That is why it works, even though you are not superCID.
QUOTE]
Where can I get CustomRUU,Could'nt find it on XDA. Is it the same as RUUwrapper and RUUupdate?
Click to expand...
Click to collapse
marcoryn said:
Where can I get CustomRUU,Could'nt find it on XDA. Is it the same as RUUwrapper and RUUupdate?
Click to expand...
Click to collapse
It may be the RUUWrapper you have, but you can get it at THIS THREAD You may already have used it though, on the one that did not give you the invalid vendor error. Use it with the nbh file. If you only have an exe, then you can use winrar to take it apart into 2 files - the ruu file (the updater) and the nbh (the ROM itself). Once you are using the right CustomRUU, try the things I mentioned in my previous post.
Other things to be sure of...
If you are using Vista, check with MrVanx guides to see what you need to do.
You must have...
ActiveSync 4.5
.NET framework 2 or higher
Thanks for ur help. Really appr. it.
When I use the CustomRuu on any nbh file I'll get the Update error (260).
If I use the same nbh file on the RUU.exe file and I choose the 2.02/2.10 option it flashes my mobile till 1%. Then I get error 274 Invalid Vendor ID.
I see on the forum a lot of people bricked there Tytn on SPL 2.03.
Is Mr. Olipro having an solution?
Have you tried these things...
Code:
Regarding the 260 error, try a couple things.
If you can, try SD flashing.
If you cannot do SD method, try using "manual bootloader" method:
- Put phone in bootloader mode
- NOW attach to USB lead
- Start CustomRUU
If that does not work, try taking the battery out for a while (5 minutes) and then try again.
todd_jg said:
Have you tried these things...
Click to expand...
Click to collapse
Yes, but without any succes
marcoryn said:
Yes, but without any succes
Click to expand...
Click to collapse
What were the specific errors for each method? I know you cannot get 260 with SD card flash method.
marcoryn said:
After flashing my locked T-mob vario dutch (for the 20st time) it now is bricked.
I tried to flash the Fun_Key_rom.
Hermes is stuck on the HTC logo 1pl-1.01 and SPL-2.03 not Super CID. (because of the warranty). I followed the thread about unbricking, but untill now no result.
I can flash it with Ruu.exe (and ruuwrapper.exe) the option 2.02/2.10 works for me untill 1% and then I get a invallid vendor ID.
I read the thread over and over again, but didn't seem to get how to unbrick it. Do I need to have a special rom? or other software?
Click to expand...
Click to collapse
You are in a quite bad situation. I am not well aware about all the new ways to backup bricked hermes; but as far as I know the only remaining possibility for you is to flash your device using the default flasher AND a rom matching your CID.
Hopefully tmobile dutch released an updated WM5 release for your phone. You should be able to flash it, setup hardspl, and flash anything you want; but in a safe way this time.
There is maybe a way to tweak the CID of cooked ROM, but don't know anything about it (and there will certainly be signing issues).
In order to get your CID and see if something matching it is available at the wiki read the wiki about mtty (as far as I remember it is something like "type 2").
fun_key said:
You are in a quite bad situation. I am not well aware about all the new ways to backup bricked hermes; but as far as I know the only remaining possibility for you is to flash your device using the default flasher AND a rom matching your CID.
Hopefully tmobile dutch released an updated WM5 release for your phone. You should be able to flash it, setup hardspl, and flash anything you want; but in a safe way this time.
There is maybe a way to tweak the CID of cooked ROM, but don't know anything about it (and there will certainly be signing issues).
In order to get your CID and see if something matching it is available at the wiki read the wiki about mtty (as far as I remember it is something like "type 2").
Click to expand...
Click to collapse
Hope Olipro will release a CustomRuu version where 2.03 can be flashed. Lot of people have probs with 2.03. Dutch T-Mob haven't released anything there is no rom availeble.
What were the specific errors for each method? I know you cannot get 260 with SD card flash method.
Click to expand...
Click to collapse
I got another error on cooked roms (26008 or something) and when I put an org. carrier rom on the card it says checking but will not install because its not a legal rom.
Because of a hardware error I had to return my Tytn today..while it still is bricked. Hope Tmob will be kind and fix this for me along with the hardware issue
Hi,
i was trying to upgrade my Hermes to WM6 and i was doing it according to mrvnx guide. First i tried the WM6 guide. Ipl was 1.01 and SPL was 1.11. Evrything went fine up until the part where the actual ROM was supposed to be flashed. The update pocess started, and i went for a smoke somewhere at 2%. When i came back, there was a message saying image file was corrupted, and Hermes was up and running. So, my first instinct was that i missunderstood something and that that guide was for phones already having WM6, so i decided to do the WM5 guide. I flashed the SPL, skipped the radio upgrade (cause i didn't know whether to use that version or the later one) and skipped to the next page. And, low and behold, there it says "Firstly download the WM5 ROM you wish to upgrade to"
And now i'm stuck and i don't know what to do. Should i get some WM5 ROM and first upgrade to it and then to WM6? Or should i go straight for WM6 ROM? If so, do i just follow the WM5 guide only using WM6 ROM or do i just flash it by the WM6 guide?
The phone still works with no problems at all. The desired WM6 ROM is Pays Full. Is it really corupted (got it from the "download full" link in the first post here), or was it my mistake?
Sim unlock and cid unlock your device then - http://pof.eslack.org/hermes-unlocker/
Download your carriers Rom (wm5 or wm6 - o2,orange,at&t etc)
then flash that.
then HARDSPL your device - http://forum.xda-developers.com/showthread.php?t=296722
then use modified updater to flash your device with the wm6/6.1 rom of your choice.. works fine for me.
2.10 bootloader with the "is it hardspl" checked and wa'la its updated
hope this helps.
Thanx for the answer. I doubt i'll find my carrier's rom, since i'm from Croatia, and i think it hasn't been posted here, and certainly hasn't been posted on my provider's site. I did make a backup before upgrading, and i have the three raw files made with itsutils. Will this do?
Also, could you please explain why i need to sim/cid unlock it? The device itself is not branded at all, i believe it's only locked to the provider's sim, and that's all. Does sim /cid unlocking cover that or is it about something else?
Thanx!
Sim unlocking = you can use other sims
CID unlocking = you can use other roms (maybe why your update is crashing)
HARDSPL = One less chance of bricking your device
as your device is still currently up and running im guessing you can do it all via that rom.
Ok, just so i don't missunderstand you, can i do what you suggested, but without flashing the carrier's rom?
you can, however you may encounter problems with wm6.1 in the future (hard resets etc)
OK to clear this thread up....
...make sure you have flashed HardSPL before continuing then...
...redownload the ROM it sounds like it has become corrupted whilst being downloaded so make sure you unzip the whole thing to a folder first then try it.
did everything like kingsizeriz told me, except i did it on the existing rom. uploaded the same rom i tried before and it worked like a charm. me and mates have been fiddling with it the whole evening and noticed no problems so far. Thanx for the help, much appreciated
Btw, one last question, is NK.EXE supposed to be 0 bytes?
Please, help me.
I have flashed my Cingular 3125 with several WM 6.1 roms without any problems. But, the last one got stuck at about 73% and was never completed.
Ever since, I can not flash the phone. No matter what I try or do, the flashing always stops at 4 or 5%, giving either the error:
ERROR [270]: UPDATE ERROR
The image file is corrupted. Please check your Update Utility.
or the error:
ERROR [294]: INVALID VENDER ID
Problem is, that i can not communicate with my phone, since it does not start up anymore (it does go into bootload mode, but if I start up 'normally', it get's stuck on the start-up screen). So i can not supercid or application unlock it (things I had done already, since I had flashed the phone several times already).
Any suggestions?
Timmoi said:
ERROR [294]: INVALID VENDER ID
Click to expand...
Click to collapse
Thats why SuperCID is strongly recommended
Timmoi said:
Problem is, that i can not communicate with my phone, since it does not start up anymore (it does go into bootload mode, but if I start up 'normally', it get's stuck on the start-up screen). So i can not supercid or application unlock it (things I had done already, since I had flashed the phone several times already).
Any suggestions?
Click to expand...
Click to collapse
Try to flash official Cingular rom via MicroSD card
My Phone was SuperCid and application unlocked.
I've tried to flash via SD card, but it doesn't work. When I try to flash a non-official Cingular rom, I get a message about a wrong certificate, and when I try to flas an official Cingular rom, I get the message "checking SD contents", but then the phone just goes to the bootloader screen.
Please, help me!
Mine did this and I was able to flash the Cingular 3125 ROM from htc.com using the USB cable... I followed the SuperCID procedure, but don't think it actually CID unlocked it since I thought the point was it'd allow me to write a non-official ROM in this situation.. but the Cingular 3125 ROM flashed ok
neutronscott said:
Mine did this and I was able to flash the Cingular 3125 ROM from htc.com using the USB cable... I followed the SuperCID procedure, but don't think it actually CID unlocked it since I thought the point was it'd allow me to write a non-official ROM in this situation.. but the Cingular 3125 ROM flashed ok
Click to expand...
Click to collapse
What do you mean exactly? Anyway, I can not follow the supercid procedure at this time, since I can not communicate with my phone. And flashing using the USB cable does not work.
Timmoi said:
When I try to flash a non-official Cingular rom, I get a message about a wrong certificate
Click to expand...
Click to collapse
It is unable to flash UNofficial roms without SoftSPL
Timmoi said:
and when I try to flas an official Cingular rom, I get the message "checking SD contents", but then the phone just goes to the bootloader screen.
Please, help me!
Click to expand...
Click to collapse
Format your microSD card to FAT32 first, and then copy NBH-file named STARIMG.nbh
Erofich said:
Format your microSD card to FAT32 first, and then copy NBH-file named STARIMG.nbh
Click to expand...
Click to collapse
I did so, but without any luck. I get a message about the certificate for unofficial roms and no result at all for official roms
PS sorry for the fist "mad" icon. Tried to delete it, but without any luck (seems i'm out of luck these days)
Same problem me too
If you have Cingular 3125, then you need to flash this rom:
http://member.america.htc.com/download/Software/RUU_STAR100_4.1.502.5_02.79.30_CWS_SHIP.exe
To flash it from microSD card, you need to open it with WinRAR (install WinRAR on your PC, then right click on file and select "Open with WinRAR"). Then get an nbh-file from it.
Erofich said:
If you have Cingular 3125, then you need to flash this rom:
http://member.america.htc.com/download/Software/RUU_STAR100_4.1.502.5_02.79.30_CWS_SHIP.exe
To flash it from microSD card, you need to open it with WinRAR (install WinRAR on your PC, then right click on file and select "Open with WinRAR"). Then get an nbh-file from it.
Click to expand...
Click to collapse
Thank you for looking in to my problem.
I've already done all that, (renamed the file to STARIMG.nbh and put it on the root of the SD card), but without any results.
Hey guys, let's see if you can help me.
My phone is dead, probably hardware failure. I last ran MAGLDR on it, and it was starting to tweak out. Random reboots, not booting up, etc. I flashed it back to stock about six months ago and it was still rebooting and dying but the rom did boot. Since then, for whatever reason and without actual use of the phone, the hardware problem has become MUCH worse. I can no longer boot into WinMo but can 1 in 20 tries boot into the HSPL screen/bootloader.
I need to send it back into HTC before the 28th of October and I don't want them to see Cotulla HSPL on screen. I've never overclocked or so much as used the phone for a long period of time, and I'm extremely gentle to electronics, so I don't know what the problem is.
I've been trying to flash back via this method.
http://www.youtube.com/watch?v=Wc89Gh0QpIY
I don't think the rom is right for my device, so I haven't used it. I own a TMOUS HD2 and the rom this guy has is a WWE rom. I don't know if this is safe to flash. Anyway, I went ahead and downloaded the latest TMOUS stock rom which unzips as an executable. I then ran the EXE, and it unzips the RUUXXXX.nbh file into C root--at least that's where I found it. I copied the file to root of the SD (FAT32) and renamed it LEOIMG.nbh. When I boot into the bootloader tri-color screen, it finds the image but only gives me an option for flashing the OS. In the youtube vid the guy flashes all sorts of things. When I flash the OS, it doesn't replace the HSPL. Does anyone have a LEOIMG that includes the SPL for a regular TMOUS? His RUU is 266 mb and mine is 5.
Any thoughts? I've scavenged the internet and I can't find a good nbh file that works.
metroidnemesis13 said:
His RUU is 266 mb and mine is 5.
Click to expand...
Click to collapse
thats wrong, you have a corrupt download or something, whats the filename before you extracted it? Go to t-mobile.com and download again. Instead of running the .exe and finding the file in c drive, you can just change the filename extension from .exe to .zip and it will open as a zip file.
I found an RUU that is 200 something MB. It has all that he had on his. It is also a TMOUS version. The problem I am having is the thing freezes after about a fifth of the installation completes, time and time again. I believe the image is good. I think the NAND on my HD2 is permanently messed up. When I access the tricolor screen now it tells me that the update failed and to please try again, and cotulla is still printed at the top. Any thoughts? Do you think HTC checks these? I sent in a Nexus One in and they sent me a new one back, no questions asked, even though the bootloader was unlocked.
I have to send this in very soon, since it expires the 28th of Oct.
all you can do is try all the tmous roms from the 't mobile test and stock roms'' thread, but not teh first three in eth list.
if all else fails you can try flashing a non tmous stock rom, which will brick teh phone, BUT will also brick bootloader, so they wont be able to see cotulla, which is the ionly thing they are interested in.
DISCLAIMER - flashign a non tmous stock rom WILL brick your tmous. The point being it will not boot at all, completely dead, so tey cant see the spl has been hacked.
Sounds like a plan.
That didn't work. The UK rom exe freezes at 1%. Returning to the bootloader I still see Cotulla's name. Ideas?
EDIT: After the third or fourth attempted flash it now says software update failed with an exclamation point and a triangle, and the only way to access the tricolor screen is to have a LEOIMG on an sd card and hit cancel. There it says cotulla. I'm going to try to brick it more with a .51 radio just to be safe.
Thanks for your help guys. The phone pretty much bricked itself. I couldn't flash the .51 radio because it stopped turning on after a while. I sent it into HTC and they repaired it, no questions asked. Now as long as it doesn't fail again... I may get an EU version because those seem to be a little bit more reliable...
Thanks again! Thread can be closed.