Database Info

RADIO 1.13 upgrade successfull! Works better.

Hey all. I'm new to the forums but have always come back here to look for technical advice on my first and only Phone PPC.
For two hours the other night I was looking for information on how to find and install radio 1.13. I finally found the files but didn't know how to install them correctly.
First, the maupdateut files found on the ftp site did not install at first. It kept giving me the "MODEL ID ERROR" message.
Second, after reading instructions on downloading the maupdateut_noid file, it finally worked.
The testimonials most of you have read about this upgrade are true. It works. I've been using the new radio for the past 2 days and the JAM performs remarkably better in all respects.
1) Bluetooth doesn't sound choppy anymore. A much stronger signal is available for sure.
2) Reception doesn't sound fluttery as it did in 1.12. There is still a little sign of degredation in the signal as i'm driving but I haven't been asking people to repeat things 3-4 times anymore. In fact, I haven't had people repeat anything yet. MUCH better, and less stressful for both parties!
3) On a route I take everyday, i use to drop signal at least 3 times. Now, I drop only once (or not at all in most cases) in a certain bad area.
PHONE DETAILS: US I-mate JAM 850mhz. ROM 1.12 with RADIO 1.13 upgade:
Instructions:
1) Download Radio 1.13 upgrade (not SD version) from ftp under Magician/Radio folder
2) Download the MAupdateUT_noid file from the ftp under Magician/Tools folder.
Try just installing the Radio folder first. If you get a MODEL_ID ERROR try this next.
1.Drag/Drop the MAupdateUT_noid file into the Radio 1.13 folder.
2.rename ONLY the HTCRUU.dll file to RUU.dll
3. then install by double clicking the NOID file.
This should complete in less than 10 minutes.
Try it and you won't be disappointed.
Also...I haven't had any problems with shortened battery life either, even with blutooth headset activated.
Thanks all!

hard reset?
Hi,
Does the procedure above require a hard reset? Do I need to install all my programs again after that?
Also, just out of curiosity, why do I need to rename the HTCRUU.dll file to RUU.dll? If I don't rename it it won't work, right?
10x in advance,
Deyan

easy upgrade to radio 1.13
I upgraded from radio 1.12 to 1.13 Thanks a lot for the easy instructions:
1) Backup Data (e.g. Sprite Backup)
2) Download Radio 1.13 upgrade (not SD version) from ftp under Magician/Radio folder
3) Download the MAupdateUT_noid file from the ftp under Magician/Tools folder.
4) Drag/Drop the MAupdateUT_noid file into the Radio 1.13 folder.
5) rename ONLY the HTCRUU.dll file to RUU.dll
6) then install by double clicking the NOID file.
7) Hard Reset (must be)
8) Restore Data

[RESOLVED] Researching how to root - Official OTA_Supersonic_1.47.651.1-1.32.651.6

This has been resolved by using the flash lite exploit to gain root access allowing the misc partition to be flashed with a downgraded main version number which allows the old leaked Eng RUU we have to be flashed!
GUI for how to root
http://forum.xda-developers.com/showthread.php?t=720565
Old and Outdated information from the Original Post listed below for historical purposes ONLY
Who is Affected: If you've flashed the official OTA update on top of a non rooted ROM or your new EVO comes loaded with it, right now it appears there is no way to obtain root...yet!
What is Patched by the OTA: Through the radio.img which the OTA flashes, it updates the Main Version in the bootloader preventing Toast's root methods from working. It also flashes back the stock recovery, removing our root access in recovery mode and ability to apply .zip files. And last of all, the OTA patches the exploit hole in /system/bin/hstools used for unrevoked1 root.
Successfully eliminating all released methods of obtaining root access.
Conclusion:
after going through all these methods with a great helpful member of the unrevoked team, joshua_, this was the final answer:
[22:34] <joeykrim> cant see to find a method to RUU the phone back down ... ive tried all the methods ive seen. any methods i missed?
[22:34] <joshua_> ok, looks like we are hosed then
[22:34] <joshua_> we have a few more tricks up our sleeve sooner or later
Future:
If you have any suggestions/ideas, please post. I might have missed a method.
We will work towards obtaining root for those with new EVOs that have the official OTA applied and those who applied the official OTA.
Details of the tested known root methods:
user debug PC36IMG.zip (toast part 1) - bootloader error - Main Version is older! Update Fail! Do you want to reboot device?
eng build PC36IMG.zip (toast part 2) - bootloader error - Main Version is older! Update Fail! Do you want to reboot device?
RUU_Supersonic_1.32.651.6 extracted rom.zip renamed to PC36IMG.zip - bootloader error - main version is older
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe - Error [140]: Bootloader version error The ROM Update Utility cannot update your Android. Please get the correct ROM Update Utility and try again.
RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe - Error [140]: Bootloader version error The ROM Update Utility cannot update your Android. Please get the correct ROM Update Utility and try again.
Stock Recovery - Apply update.zip - clockwork recovery update.zip - E:failed to verify whole-file signature E:signature verification failed
flash_image (flash boot or mtd-eng.img) - copied to /sdcard, but sdcard is mounted with noexec. partition with write access for non-root user and allows executing is /data/local . flash_image can't write to the partitions w/o being run with root permissions. chownto and chown of flash_image to user root - permission denied.
##786# - Reset - doesn't seem to effect much in the way of bootloader version ...
Modifying PC36IMG.zip - using a hex editor to attempt at changing the MainVer stored in the android-info.txt, if any bit changes, it seems to fail the validation by the bootloader.

I tried almost all of these after the OTA hit my wifes phone. No dice. Subscribed to further updates on this thread.

I created a PC36IMG.zip file which contained the .6 releases wimax image and the android-info.txt file from the new update. I was then able to successfully flash it with hboot by placing it in the root of the sdcard and doing a down volume power on boot. It found the pc36img.zip file, verified it, asked me if I wanted to flash it. When I selected yes, proceeded to do so. It then reported the flash as having been successful.
I can't tell if the flash actually worked because I don't know where to check the wimax version info...
I don't know if this worked because the phone doesn't care to check the MainVer when flashing just the wimax image or if it did it because I pulled a fast one with the android-info.txt file swap.
I extracted the wimax image from the RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe file.
I wonder if it would be possible to pull the same trick with the larger subset of images from the rooting pc36img.zip files. i.e. swap out the android-info.txt files...

frankenstein\ said:
I created a PC36IMG.zip file which contained the .6 releases wimax image and the android-info.txt file from the new update. I was then able to successfully flash it with hboot by placing it in the root of the sdcard and doing a down volume power on boot. It found the pc36img.zip file, verified it, asked me if I wanted to flash it. When I selected yes, proceeded to do so. It then reported the flash as having been successful.
I can't tell if the flash actually worked because I don't know where to check the wimax version info...
I don't know if this worked because the phone doesn't care to check the MainVer when flashing just the wimax image or if it did it because I pulled a fast one with the android-info.txt file swap.
I extracted the wimax image from the RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe file.
I wonder if it would be possible to pull the same trick with the larger subset of images from the rooting pc36img.zip files. i.e. swap out the android-info.txt files...
Click to expand...
Click to collapse
im guessing the only reason it allowed you to flash a PC36IMG.zip which wasn't HTC signed is because you're using the hboot from the eng build of the PC36IMG.zip which doesn't check for HTC signatures on the PC36IMG.zip file. Not sure if it looks at the MainVer or not ...
once you're on a stock hboot, the PC36IMG.zip file has to be signed by HTC in order to flash!

I think in order for this to be patched, the bootloader code needs to be disassembled between the two versions to find out what bytes were patched and then either remove the code that checks for HTC signing or find a way to circumvent it.
We had to do things like this when working with mach_kernel when we got ahold of the first developer build of OS X for Intel. It was a pain in the ass and took weeks before we cracked the kernel.
There is even more risk with this though since tampering with the bootloader can definitely permanently brick devices.

joeykrim said:
If you've flashed the official OTA update or your new EVO comes loaded with it, right now it appears there is no way to obtain root...yet!
after going through all these methods with a great helpful member of the unrevoked team, joshua_, this was the final answer:
[22:34] <joeykrim> cant see to find a method to RUU the phone back down ... ive tried all the methods ive seen. any methods i missed?
[22:34] <joshua_> ok, looks like we are hosed then
[22:34] <joshua_> we have a few more tricks up our sleeve sooner or later
If you have any suggestions/ideas, please post. I might have missed a method.
We will work towards obtaining root for those with new EVOs that have the official OTA applied and those who applied the official OTA.
Here are details of the tested methods:
user debug PC36IMG.zip (toast part 1) - bootloader error - Main Version is older! Update Fail! Do you want to reboot device?
eng build PC36IMG.zip (toast part 2) - bootloader error - Main Version is older! Update Fail! Do you want to reboot device?
RUU_Supersonic_1.32.651.6 extracted rom.zip renamed to PC36IMG.zip - bootlaoder error - main version is older
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe - Error [140]: Bootloader version error The ROM Update Utility cannot update your Android. Please get the correct ROM Update Utility and try again.
RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe- Error [140]: Bootloader version error The ROM Update Utility cannot update your Android. Please get the correct ROM Update Utility and try again.
Stock Recovery - Apply update.zip - clockwork recovery update.zip - E:failed to verify whole-file signature E:signature verification failed
flash_image (flash boot or mtd-eng.img) - copied to /sdcard, but sdcard is mounted with noexec. only partition with write access for non-root user and allows executing is /sqlite_stmt_journals . flash_image can't write to the partitions w/o being run with root permissions. another words, need root access to use flash_image
##786# - Reset - doesn't seem to effect much in the way of bootloader version ...
Click to expand...
Click to collapse
since my frien did the OTA update yesterday and "bricked" his phone i have been trying to fix the phone (i have access to bootloader so it seems to me that maybe, just maybe i can save the phone) anyways, i have been getting a lot of the same error messages anytime i try to update/load any stock rom via bootloader.
what my question is, is there a way to take a 1.47.651.1 rom/image and put it into an ruu? i have looked all over htc's website, but they don't even acknowlege the existence of the evo, at least not that i can find.

joeykrim said:
flash_image (flash boot or mtd-eng.img) - copied to /sdcard, but sdcard is mounted with noexec. only partition with write access for non-root user and allows executing is /sqlite_stmt_journals . flash_image can't write to the partitions w/o being run with root permissions. another words, need root access to use flash_image
...
Click to expand...
Click to collapse
Just curious here, regarding the above step, if you had access to a phone that was already rooted, could you use your sdcard in that phone to copy the files into /data and then transfer the sdcard back to the unrooted phone to flash it then?

Sorry for the long multi quote, there are quite a few good ideas and I wanted to make sure I explored each of them as far as the original poster intended.
EtherealRemnant said:
I think in order for this to be patched, the bootloader code needs to be disassembled between the two versions to find out what bytes were patched and then either remove the code that checks for HTC signing or find a way to circumvent it.
Click to expand...
Click to collapse
interesting ... circumventing the HTC signature check would be perfect and essentially give us an eng build bootloader.
in the RUU.exe rom.zip files, the android-info.txt indicate the MainVer along with a separate hboot.img file. the official OTA didn't have an hboot.img file. It only had a radio.img file which must have updated the MainVer value.
Not sure where on the phone this MainVer value is stored? in the radio?
you're suggesting, compare the bootloader, which is obviously stored somewhere in radio.img as thats the only file being flashed thru the OTA which increments the bootloader version number, against an older radio.img to attempt and find which bytes were changed for the version number?
The radio.img files are all around 22mbs ... ugh
if we're able to find the change in version number on the radio.img, not sure how it would help in flashing over it?
i was kind of thinking down these lines...since the bootloader checks the version number of any file it attempts to flash, the version number is going to be the key.
if we're able to increment (or temp change) the main version number in the file being flashed w/o messing up the htc signature, that could work.
2002wrex said:
what my question is, is there a way to take a 1.47.651.1 rom/image and put it into an ruu?
Click to expand...
Click to collapse
i've heard this was often done back in the WinMo days but i haven't seen anything on this board regarding this approach. if you have any detailed information, we could def look into it!
unknown_owner said:
Just curious here, regarding the above step, if you had access to a phone that was already rooted, could you use your sdcard in that phone to copy the files into /data and then transfer the sdcard back to the unrooted phone to flash it then?
Click to expand...
Click to collapse
very clever concept!
i'm not 100% sure on all the different approaches in the suggestion, but here are the ones it prompted me to explore.
unfortunately, every time the /sdcard is mounted on the phone, its mounted as noexec, meaning no files located on the /sdcard can be executed like programs.
also the /sdcard is mounted with uid=1000 and gid=1015 meaning all files mounted on the /sdcard have their uid/gid overwrote so none of them are allowed root ownership.
without being able to "su" to root access, we aren't able to run any programs with root access.
trying to chownto flash_image to any reference file as root results in:
chownto flash_image /system/bin/chown
Can't change user/group to root!
chown root flash_image
Unable to chmod flash_image: Operation not permitted
if i missed the suggested approach, could you elaborate?

Oh boy...... I thought I was alone in this. I try everything I can and now gave up. Any one can rooted this new OTA please let me know. I really need to downgrade from this.

Made me think of a problem that happened with the Directivo a few years back...
ht t p://dealdatabase.com/forum/showthread.php?t=22154
I was looking around, trying to figure out some way to hack the hdvr2 w/o modifying the prom. I recalled something from the xbox-linux team's presentation for CCC, which was something close to "once you break the chain of trust, the box is forever compromised." I thought to myself: "self, if we can load one kernel via BASH_ENV, why can't we load a second kernel?"
Click to expand...
Click to collapse
So, is there a way we could compromise the kernel? If so, then...

Subscribed...
Not really interested in rooting until froyo is working, and I could really use the wifi fixes this OTA is supposed to offer, but I'll hold off installing it until we know it can eventually be rooted.

Mikesus said:
http://dealdatabase.com/forum/showthread.php?t=22154
So, is there a way we could compromise the kernel? If so, then...
Click to expand...
Click to collapse
i read thru the thread. im not clear on how they used BASH_ENV or any other method to load a 2nd kernel.
unfortunately, i think we have an extra layer of security that they dont. thanks HTC!
without nand unlocked on the kernel partition no data can be stored there including a 2nd kernel.
appreciate the link and info. perhaps the ideas or concepts will spur some innovation!

joeykrim said:
i've heard this was often done back in the WinMo days but i haven't seen anything on this board regarding this approach. if you have any detailed information, we could def look into it!
Click to expand...
Click to collapse
the thing about winmo ruu's (here's a topic i DO know well) is that they are always in a zip. you decompress the zip and have access to all the files. one of them will be the ruu, the rest are all the supporting files/images/rom. all of the android ruu's seem to come as on large exe that doesn't allow access to the files, it merely runs itself. in the winmo days if you got a rom with no ruu, and didn't want to flash from SD, you just took someone elses ruu and dumped the rom image in to the decompressed folder containing the ruu.
i appreciate the help joey, obviously you are busy with your own problems and a lot of people around here just throw you the old "SEARCH BUTTON" response. any help is greatly appreciated!

2002wrex said:
the thing about winmo ruu's (here's a topic i DO know well) is that they are always in a zip. you decompress the zip and have access to all the files. one of them will be the ruu, the rest are all the supporting files/images/rom. all of the android ruu's seem to come as on large exe that doesn't allow access to the files, it merely runs itself. in the winmo days if you got a rom with no ruu, and didn't want to flash from SD, you just took someone elses ruu and dumped the rom image in to the decompressed folder containing the ruu.
Click to expand...
Click to collapse
interesting again .. so the RUU .exe files for android, do have a payload stored in a rom.zip file which is dumped to a temp directory after the RUU .exe starts and before it finishes.
now, the rom.zip files have been pulled and posted in each of the two RUU .exe threads we currently have. these rom.zip files do contain all .img files which are flashed to the phone. the catch is though, just as the PC36IMG.zip files used in root, these rom.zip files seem to have a special HTC signature (checksum?) in their header.
if you open these rom.zip files from the RUU in winzip, it will error out, but using 7zip, they open just fine.
im new to HTC, this is my first HTC android phone and its almost been 4 weeks so this is as much as i know. it seems, if we're able to alter these rom.zip files either used in the RUU .exe or naming them PC36IMG.zip flashed thru the bootloader and the phone excepts them, we would be golden!
to help save you some searching and let you see what im talking about, here is the latest RUU rom.zip file
http://www.joeyconway.me/evo/stock/RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_rom.zip

Subscribed, I was able to Order my EVO today so I will be watching for development. I pledge my donations to whoever is able to figure it out. I really appreciate the efforts of this community.

I second that pledge for donations! I, like many others here, updated while knowing that I probably shouldn't have. I knew better...

Subscribed.
Thanks for all the effort and work. I hope ya'll get it figured out.

dang, I just got my evo yesterday and got the update message so I thought it'd be ok to update it as I thought it might have been old.
Came home and was excited to do all my customization and tweaks, but w/ no prevail

So my local best buy will not give the phone to the customer without pushing the new OTA to it :/
Apparently all of the stores will be doing this per Sprint and HTC's request.

EtherealRemnant said:
So my local best buy will not give the phone to the customer without pushing the new OTA to it :/
Apparently all of the stores will be doing this per Sprint and HTC's request.
Click to expand...
Click to collapse
Try calling them ahead of time before picking it up and asking if you can just swing by and pick it up yourself and call Sprint to activate yourself. Tell them you are in a rush, make up a story, and see if they just let you pay for it and run.

(Q) how to update RIL and Radio

Hey guys, if someone could put together a unified guide on updating to the latest ATT RIL and Radio I would really appreciate it. I've seen different information scattered throughout the dev/rom section but was hoping someone could make a post in general. (Instead of a bunch of people cluttering up rom sections.
Thanks in advance!
Sent from my InspireDesire 4GHD

For the RIL, open up your ROM Manager, go to download roms, gtg465x, and select the RIL option.
For the radio, put the PDIMG (or whatever its named; don't want to look it up) on your root directory of the SDCard and bot into recovery (volume up + power button) and it should automatically start flashing it.
Note, just because its the latest version doesn't necessarily mean its good. Also try to use the corresponding RIL with its radio version.

Printerscape said:
For the RIL, open up your ROM Manager, go to download roms, gtg465x, and select the RIL option.
For the radio, put the PDIMG (or whatever its named; don't want to look it up) on your root directory of the SDCard and bot into recovery (volume up + power button) and it should automatically start flashing it.
Note, just because its the latest version doesn't necessarily mean its good. Also try to use the corresponding RIL with its radio version.
Click to expand...
Click to collapse
Thanks for the reply! If anyone has anything to add feel free to post.
Sent from my InspireDesire 4GHD

I wouldn't recommend the above method. The RILs have to correspond to the radio. Check the RCMix 6.1 thread and look for the sig file for Cocchiarraro. You'll find he has a link to matched sets of radio/ril archives. I'd also recommend you give the RCM rom a shot. It's awesome, and also available through ROM manager - look for TeamRC.

BillTheCat said:
I wouldn't recommend the above method. The RILs have to correspond to the radio. Check the RCMix 6.1 thread and look for the sig file for Cocchiarraro. You'll find he has a link to matched sets of radio/ril archives. I'd also recommend you give the RCM rom a shot. It's awesome, and also available through ROM manager - look for TeamRC.
Click to expand...
Click to collapse
What part of the above method do you recommend against?
The RIL part of the post refers to an RIL flasher that gtgx65x made for his Rom that will also work with other roms. It just lets you choose your installed radio from a list, and then flashes the correct matching RIL for you.
The rest of that post does leave a few questions in my mind though.
Inspired Ace 1.0.1¦ XDA Premium

Scott_S said:
The rest of that post does leave a few questions in my mind though.
Click to expand...
Click to collapse
Heh, I was being way too general... all you need is to download the correct P98IMG.zip file, replace the radio.img with what you want in there, and just put it on the root directory of the SDCard.
That's how I've been doing it, and it's always been successful...

Here are some links to the latest radios ( in the form of PD98IMG.zip) and RILs.
http://wiki.cyanogenmod.com/index.php?title=Support_Downloads#HTC_Ace
http://forum.xda-developers.com/showthread.php?t=1040986

Printerscape said:
Heh, I was being way too general... all you need is to download the correct P98IMG.zip file, replace the radio.img with what you want in there, and just put it on the root directory of the SDCard.
That's how I've been doing it, and it's always been successful...
Click to expand...
Click to collapse
That's how I've been doing it too, and how I was planning on doing it again. Is there something wrong with that method?

Printerscape said:
Heh, I was being way too general... all you need is to download the correct P98IMG.zip file, replace the radio.img with what you want in there, and just put it on the root directory of the SDCard.
That's how I've been doing it, and it's always been successful...
Click to expand...
Click to collapse
That's how I've been doing it too, and how I was planning on doing it again. Is there something wrong with that method?

Does anyone have the 26.09.04.1 radio is ruu format?

I want to use Ace's Hack Kit to flash my first rom and radio on this brand new device. The recommended radio for coredroid is 26.09.04.1. I can only find it in an img file. I was hoping someone had converted it to RUU, so I can follow the steps in the "effen manual" in the hack kit.

Try this thread:
http://forum.xda-developers.com/showthread.php?t=1106324

I could be wrong but they don't come in ruu, do they? Isn't that a Windows Mobile phone thing? Radios for Android are zip format and installed with the bootloader.

kimtyson said:
I could be wrong but they don't come in ruu, do they? Isn't that a Windows Mobile phone thing? Radios for Android are zip format and installed with the bootloader.
Click to expand...
Click to collapse
I'm assuming he meant PD98IMG.ZIP format, but I might be wrong. Guess I should have clarified.

volumnus said:
I want to use Ace's Hack Kit to flash my first rom and radio on this brand new device. The recommended radio for coredroid is 26.09.04.1. I can only find it in an img file. I was hoping someone had converted it to RUU, so I can follow the steps in the "effen manual" in the hack kit.
Click to expand...
Click to collapse
Here's what you can do. In the ace-hack-kit.zip, you'll find a folder called Tools. Open it and then open the folder called Radio. Here you will find a PD98IMG.zip file, and inside this .zip you will find a radio.img file. You can replace this radio.img file with the radio.img of your choosing, then put your newly created PD98IMG.zip back in tools\radio. Make sure you're not changing the compression of anything and when you perform the hack kit, it will flash the radio you want

Thanks.
homeslice976 said:
Here's what you can do. In the ace-hack-kit.zip, you'll find a folder called Tools. Open it and then open the folder called Radio. Here you will find a PD98IMG.zip file, and inside this .zip you will find a radio.img file. You can replace this radio.img file with the radio.img of your choosing, then put your newly created PD98IMG.zip back in tools\radio. Make sure you're not changing the compression of anything and when you perform the hack kit, it will flash the radio you want
Click to expand...
Click to collapse
I installed the radio. Success. Now all I have to do is wait for coredroid 6.8 to be debuted tonight and install it from recovery mode, and I think I'm good to go. You don't have to install the rom BEFORE the recommended radio do you? I didn't think it mattered.

No your good to go. Coredroid should have the proper ril for the radio. Just flash coredroid using clockwork and have fun. Coredroid has got to be one of the best looking tons out, good luck
Sent from my Desire HD using XDA App

Trouble with Hack Kit.

I have downloaded the radio I want from the radio thread. I am putting the zip in the romzip folder and renaming it rom.zip. What am I doing wrong?

What error are you receiving? Make sure USB debugging is on.
An alternative is to name it PD98IMG.zip and flash the radio through hboot.
Make sure to verify the md5sum before flashing
Sent from my TARDIS using XDA App

volumnus said:
I have downloaded the radio I want from the radio thread. I am putting the zip in the romzip folder and renaming it rom.zip. What am I doing wrong?
Click to expand...
Click to collapse
So you're saying you dispossessed one of the radios from the inspire radio thread in the dev section, correct?
If so, it sounds like you are going through some unnecessary steps.
Once you download one of the radios from the above-mentioned thread, you put that file, which is already named correctly, PD98IMG.zip, into the root of your SD card.
Verify the MD5 of that PD98IMG.zip file, checking it against that posted for the radio.
If it is identical, proceed...
I have fastboot unchecked, reboot the phone and get into hboot.
Select bootloader (I think. I don't do it THAT often. )
After a second or two, it should look for the file, and scan it.
Push the corresponding volume button to confirm applying the update, let it do its thing.
Reboot.
Confirm baseband reflects the newly flashed radio.
Flash appropriate RIL for the radio, if necessary, via cwr.

WHAT'S MD5? Is it important for us? Im just flashing many radios to test which one works best for me.
Sent from my Desire HD using XDA App

MD5 checksum is a way to verify if the file has been corrupted in either download or transfer and yes it is important, especially with the radio if you flash a radio; at the least you will not be able to flash the radio, at worst with a bad file you have the opportunity to Brick you phone! When loading roms patches ect. using md5 ensures a proper file for install. If your in the us I would suggest sticking with the latest stock AT&T radio until you settle on a rom and then only change if you don't have the performance you think you should have.