Database Users

Can anybody help here! HTC Touch/Vogue/xv6900 Custom ROM Flash

Alright, I've been in the process of trying to flash the ROM on my Vogue. I've been doing this over at PPCGeeks, and thought I try my luck for help with good people of xda.
Here is the comment I posted over there:
Alright, I've been reading and reading, can't find the answer, so hopefully someone can give me a detailed answer.
I ran the unlocker, to flash on OMJ Vogue ROM, with the Rev-A and GPS capabilities. During the process when the HTC ROM updater came on, the device wouldn't reconnect (I tried about 5 times, hard reset and starting from scratch). After waiting at the updater for about 10 minutes, I hit next and this time, as mentioned above, it said it was replacing the ROM image, but was blank. Meanwhile my phone is on the bootloader reading SPL-2.00.CoKe, after the updater went through the process, all of a few seconds, it performed the hard reset.
Now I have entered the bootloader to see SPL-2.31.CoKe, even after two hard resets, one being the auto, and one manual. The phone starts as it should, but once I turn it off, it won't power back on. I believe I saw a fix for this, but can't remember.
My biggest questions are, what can I do now? Is this normal, and I should continue to flash from here?
Anybody here know what I can do?
Thanks!

Here is a good place to start:
http://forum.xda-developers.com/showthread.php?t=398571
or even the entire Vogue subforum.

Wow, thanks junior, this is a bit more of a specific question.

Sounds like you did not do the radio upgrade that is necessary. I agree though, posting in a forum that is specific to your device/problem is best. And, I know for a fact, that there are numerous threads/posts on this subject at ppcgeeks.

try the ffg
http://forum.xda-developers.com/showthread.php?t=394039
or
http://forum.xda-developers.com/showthread.php?t=387960

colonel00 said:
Sounds like you did not do the radio upgrade that is necessary. I agree though, posting in a forum that is specific to your device/problem is best. And, I know for a fact, that there are numerous threads/posts on this subject at ppcgeeks.
Click to expand...
Click to collapse
That's the problem though, I couldn't even get to the radio part yet. I think the issue was with the reconnecting the device to ActiveSync, during the unlocking proccess?
Now, is there a way to complete this step through an SD card. Using ImCokeMan's 2.31 Vogue unlocker.

I went through the exact same thing, they're right about the radio
Use the official leaked sprint rom, it's an exe. Run it and flash. Then, DON'T LET IT BOOT UP!!! Immieaditely put it back in CoKe, and flash your desired ROM. When the vogue first starts up, it should say under those numbers that pop up R 3.37.15

xd1936 said:
I went through the exact same thing, they're right about the radio
Use the official leaked sprint rom, it's an exe. Run it and flash. Then, DON'T LET IT BOOT UP!!! Immieaditely put it back in CoKe, and flash your desired ROM. When the vogue first starts up, it should say under those numbers that pop up R 3.37.15
Click to expand...
Click to collapse
Awesome, I'm glad someone here has knowledge on this ! Ok, but from this point, the device has been hard reset, still with it showing the SPL as 2.31.CoKe, so from here should I run the Radio exe, it seems that I never finished the first step, which is completeing the unlocker tool, is this normal?

Official Eris RUU

Just in case you need it, here it is.
http://www.pcdphones.com/downloads/Eris MR1.zip

This is the Dec 11th update?

Yes but it is the full ruu not just the update if you use this you will loose all of you data and settings.

This may be a work around for those experiencing problems since the update.

this works great for the phone os issues caused by the update. but there are apps in the market that cause your phone to freak out. it's not the eris's fault or the apps fault. when upgrades happen like the way htc did this one it bound to cause some apps to freak out cause of the update. htc has no obligaton to support these apps either that's on the app creator to fix htc is only fixing it's own issues.
this is the reason why htc doe not like quick patches to thier phones. if you look at the history of the dream/G1 this is the first quick patch other than 1.30. because 1.29 allowed root level commands in the contacts area but that was to fix that problem not to fix customer complaints. i just hope htc goes back to the we'll get you a patch when we get you a patch mentality. cause it seems less problematic that way.
just my feelings

binny1007 said:
Yes but it is the full ruu not just the update if you use this you will loose all of you data and settings.
Click to expand...
Click to collapse
Thanks! I did the manual update using RUU as soon as it came out and actually have been pretty lucky...None of the freezing up etc issues that people are having.

Anyone have an updated link?

Hungry Man said:
Anyone have an updated link?
Click to expand...
Click to collapse
I've got the EXE if you have something/somewhere I can upload it to?

You could use megaupload? Or try uploading it to this site aka xda?
If I were to just install the 2.1 leak wouldn't that do basically the same thing? Or is this easier?

The RUU in this thread was for MR1, which is still Android 1.5. I think you're looking for the newer RUU: http://shipped-roms.com/shipped/Des...WWE_2.36.605.1_release_signed_with_driver.exe

Ok so if I download that what do I do with it to unroot?

Hungry Man said:
Ok so if I download that what do I do with it to unroot?
Click to expand...
Click to collapse
Attach your phone to your computer with the USB cable, and run the RUU program in Windows. It will wipe all data from your phone and return it to the stock 2.1 software, complete with the 1.49 S-ON bootloader, the default recovery image, and no root.
If you want to re-root from there, you'll have to use one of the new root methods, since your phone will be identical to the phones that Verizon is currently shipping out (with Android 2.1), not the original Android 1.5 version of the software.

Awesome, thanks a ton.

i am trying to use this to unroot my phone so i can send in for a replacement and it goes through all the checks and verifications. it rebbots to the bootloader then while updating signiture i get error 140 bootloader version error saying the rom update utility cannot update your android phone please get the correct rom update utility and try again?? if this doesnt work is there another easy way to unroot?

yamaha83 said:
i am trying to use this to unroot my phone so i can send in for a replacement and it goes through all the checks and verifications. it rebbots to the bootloader then while updating signiture i get error 140 bootloader version error saying the rom update utility cannot update your android phone please get the correct rom update utility and try again?? if this doesnt work is there another easy way to unroot?
Click to expand...
Click to collapse
same here, ruu fails

sleepyastronaut said:
same here, ruu fails
Click to expand...
Click to collapse
If you get a version error, you need to first run jcase's "Flash any RUU" hack.**
Note that (strictly speaking) jcase should have entitled his post "Flash any PB00IMG.zip ROM" because of another small complication: some ROMs do not have a compatible version of the "reboot" command (the RUU utility first uses the reboot command to put the phone into oem-78/RUU mode). If you insist on using the RUU utility, you can overcome this minor problem by first flashing a compatible ROM, such as PlainJane.
But, it is just as easy to flash the Leak-V3 PB00IMG.zip ROM, which produces the identical result as the "Official" RUU.
Note also that if you have used the RUU utility, them you already have USB drivers installed on your PC, and so getting adb running on the PC does not require setting up the full-blown SDK (you don't need Eclipse set up) : just download the SDK, unzip it, and you are ready to rumble.
To reiterate: if you get a version error, you need to run jcase's "Flash any RUU" hack first; after that, you can either run the HBOOT+Leak-V3 PB00IMG.zip install, or the RUU. The PB00IMG.zip method has no dependencies, and is somewhat easier.
bftb0
** Note there is a minor mistake in the instructions given in the OP of the "Flash any RUU" thread; be sure to read the first dozen posts or so - the correction is given.

thenestor said:
The RUU in this thread was for MR1, which is still Android 1.5. I think you're looking for the newer RUU: http://shipped-roms.com/shipped/Des...WWE_2.36.605.1_release_signed_with_driver.exe
Click to expand...
Click to collapse
This is the exe that I used to restore my Eris from Kaos Froyo to Stock 2.1. All I did was run the exe file and follow simple prompts. It took about 10-15 mins and the Eris was ready to return to VZW.
Very nice work, Thank you Devs!!!

Does flashing RUU replace the kernel and/or radio? Just wondering

jsuh said:
Does flashing RUU replace the kernel and/or radio? Just wondering
Click to expand...
Click to collapse
I'm pretty sure it replaces both. That's how people discover new kernel and radio versions.
Sent from my xtrSENSE Eris using XDA App

Any idea what I'm doing wrong here?
Windows 7 SP1 x64

HTS HD2 - Cooked ROM Bricked

I tried to cook my own ROM and when I installed, the installation was successful. But after that my phone does not start. when I click the power button, the phone does not boot.
My ROM size was close to 300 MB.
Any help is appreciated.

mukesh_thiru said:
I tried to cook my own ROM and when I installed, the installation was successful. But after that my phone does not start. when I click the power button, the phone does not boot.
My ROM size was close to 300 MB.
Any help is appreciated.
Click to expand...
Click to collapse
Phone doesn't boot? What do you mean doesn't do anything or gets stuck?
If your device turns on you could try to get in bootloader by holding volume down when turning on the device. If that works you can connect to usb and flash another rom

When I hit the power button nothing happens, the screen is black, the device does not start. No bootloader, no led light nothing, I tried hard reset, I tried the reset button.
When I was installing the custom ROM the battery was full. When I connect to USB, the computer says some Qualcomm device thats it.

If you cant boot in bootloader, then its screwed. But you said your pc sees it as qualcom device...so it probably ok.
Just put it in bootloader, and flash a stock ROM.

PC shows as "qualcomm cdma technologies msm". But nothing else not going to bootloader

Did your ROM had a radio in it or only the OS?

I guess only OS, I think I did not have Radio

Did you tried to leave the battery?
Which Original stock rom did you used for cooking your own? Have you a link?
Did you already searched in forum for a possible fix?
i found some links http://www.google.com/cse?cx=partne...mqefhnf&ie=ISO-8859-1&q=hd2+bricked&sa=Search
Give us as more infoes as you can.
HD2: Tmous or Htc brand?
HDSPL? Have you installed one?

It a tmobile. I used the Oskitchen and downloaded a stock ROM to start. I removed some of the items that I did not want, then after I did "start building". I took the "RUU_Signed_0409" from the output folder. I flashed this to my device.
HDSPL - http://forum.xda-developers.com/showthread.php?t=611433 I followed this tutorial.
Can you please let me know what you mean by "Did you tried to leave the battery?"

Leave the battery means Take out the battery for some times and then return it inside.
Did you dump a TMOUS Stock rom, right?
mukesh_thiru said:
It a tmobile. I used the Oskitchen and downloaded a stock ROM to start. I removed some of the items that I did not want, then after I did "start building". I took the "RUU_Signed_0409" from the output folder. I flashed this to my device.
HDSPL - http://forum.xda-developers.com/showthread.php?t=611433 I followed this tutorial.
Can you please let me know what you mean by "Did you tried to leave the battery?"
Click to expand...
Click to collapse

Yes tmobile stock ROM

mukesh_thiru said:
It a tmobile. I used the Oskitchen and downloaded a stock ROM to start. I removed some of the items that I did not want, then after I did "start building". I took the "RUU_Signed_0409" from the output folder. I flashed this to my device.
HDSPL - http://forum.xda-developers.com/showthread.php?t=611433 I followed this tutorial.
Can you please let me know what you mean by "Did you tried to leave the battery?"
Click to expand...
Click to collapse
Can you please compress the ROM and upload it somewhere so we can take a look? If you didn't select splash screen or radio the ROM should contain only the OS section and therefore be safe to flash.

MOD EDIT: removed link because not safe,PM OP for link. thanks.

@ Airxtreme:
Did you see his prvious post? See below, he hisnt totaly sure by Radio.
Most TMOUS mobiles Rom upgrade failure are due to flash a non compatible RADIO , its not safe to flash the rom linked.
Im removing the link, if someone wanna try what Airxtreme suggested, please share it by PM....sorry but i do not want some noobs complaining for his phone bricked.
mukesh_thiru said:
I guess only OS, I think I did not have Radio
Click to expand...
Click to collapse
airxtreme said:
Can you please compress the ROM and upload it somewhere so we can take a look? If you didn't select splash screen or radio the ROM should contain only the OS section and therefore be safe to flash.
Click to expand...
Click to collapse

mukesh_thiru said:
MOD EDIT: removed link because not safe,PM OP for link. thanks.
Click to expand...
Click to collapse
Sorry but the archive seems to be corrupted however from the part I could extract it looks like the ROM file except for the fact that it's 400mb big (but it shouldn't be a problem if yours is a TMOUS phone) has only the OS section and that means it should have been safe to flash. Try removing the battery as suggested, unless you have issues with your computer's USB or some other application messing up the RUU updater the phone shouldn't have been permanently bricked also when you turn it on to enter the bootloader mode try doing it with the phone not connected to the computer maybe it just doesn't like the USB port.

af974 said:
@ Airxtreme:
Did you see his prvious post? See below, he hisnt totaly sure by Radio.
Most TMOUS mobiles Rom upgrade failure are due to flash a non compatible RADIO , its not safe to flash the rom linked.
Im removing the link, if someone wanna try what Airxtreme suggested, please share it by PM....sorry but i do not want some noobs complaining for his phone bricked.
Click to expand...
Click to collapse
From what I saw there is no radio in there and the archive wouldn't even extract so I don't think there is any risk about somebody flashing that file.

Yeah i see that it is corrupted, but you know ....i have seen some recent post in Kaiser forum with people with Different phones then the Kaiser, asking in Spl thread how to install it on their phone....so better dont risk imo
airxtreme said:
From what I saw there is no radio in there and the archive wouldn't even extract so I don't think there is any risk about somebody flashing that file.
Click to expand...
Click to collapse

[Q] New Rom help

So i have a pretty much newbie question. I figured out how to load a new rom on my tp2 I am currently using Energy Rom, rom date 3/15/10 with manila 2.520161332.0, radio version 4.4825.20. I am through at&t and i was wondering how i load the newest Energy rom and which one that is? maybe someone could post a link with it, if they have time. Also what do I do for steps as in for loading a new rom when i already have a burnt one on my tp2. Sorry such a newbie question hope I can get some help from experts, thank you.

Might want to look in the ROM Development subforum. The process is covered in detail there.

Go here and read the fifth thread down. -> http://forum.xda-developers.com/forumdisplay.php?f=490

cajunflavoredbob said:
Go here and read the fifth thread down. -> http://forum.xda-developers.com/forumdisplay.php?f=490
Click to expand...
Click to collapse
Thank you for the response, I already did my first flash from stock to energy rom dinik. question is do I have to do the hard spl again? I was reading about task 29 Do i do that to clear this current rom? Then load the new one? I guess my main question what steps do I follow to replace a out dated flashed custom rom?

nitegmoney said:
Thank you for the response, I already did my first flash from stock to energy rom dinik. question is do I have to do the hard spl again? I was reading about task 29 Do i do that to clear this current rom? Then load the new one? I guess my main question what steps do I follow to replace a out dated flashed custom rom?
Click to expand...
Click to collapse
Ah, that's a much more clear question. Hard SPL is permanent until you flash the stock one back for whatever reason. Basically, it'll stay there until you remove it yourself. task29 is a good idea to do between ROM flashings. It clears out and formats the internal memory. It prevents the device from retaining traces of the old ROM when you flash the new one. Use the order listed below.
1. back up any important data and reboot into bootloader (hold voldown while pressing reset)
2. run task29
3. flash new ROM
4. hard reset (hold talk/send and end while pressing power button)
5. set up the new device
The hard reset is kind of optional, but I do it anyway since I'm kind of OCD like that.

1. back up any important data and reboot into bootloader (hold voldown while pressing reset)
2. run task29
3. flash new ROM
4. hard reset (hold talk/send and end while pressing power button)
5. set up the new device
The hard reset is kind of optional, but I do it anyway since I'm kind of OCD like that.[/QUOTE]
thank you very much this should help just a couple questions (sorry I was very cautious when flashing my first rom as well, because I didn't want to screw anything up).
1. If i dont wanna save any data besides whats on my sim and sd card just remove both before starting any of the 5 steps?
2. Are there any roms with cookie 2.0?
3. In step one you say reboot into bootloader (hold volume down while pushing reset, which button is reset?
4. Task 29 I jus run on my comuter i take it while synced?
Sorry I'm very cautious lol if you cant tell, just want to make sure I dont mess anything up.
Thank you for your help I feel about half way ready to attempt again lol.

nitegmoney said:
thank you very much this should help just a couple questions (sorry I was very cautious when flashing my first rom as well, because I didn't want to screw anything up).
1. If i dont wanna save any data besides whats on my sim and sd card just remove both before starting any of the 5 steps?
2. Are there any roms with cookie 2.0?
3. In step one you say reboot into bootloader (hold volume down while pushing reset, which button is reset?
4. Task 29 I jus run on my comuter i take it while synced?
Sorry I'm very cautious lol if you cant tell, just want to make sure I dont mess anything up.
Thank you for your help I feel about half way ready to attempt again lol.
Click to expand...
Click to collapse
All of these questions could have been answered if you read some of the threads available in the ROM development area. You're lucky I'm feeling generous today.
1. Removing the SIM and SD is optional. I never do, but some people swear by it. It's up to you whether you do or not.
2. There are lots of them. Have a look around. You could always install it over an older CHT version or onto a ROM without CHT at all.
3. There should be a tiny reset button hole that your stylus will fit into on the right side of the device under the battery cover. If you have a T-Mobile device, it's right next to the noise-canceling mic on the left side. You should already be in bootloader when you flash anything, including task29.
4. task29 has two files. The *.nbh file can be anything at all. It makes no difference. The *exe that comes with the download is what does the formatting. You should already be in the bootloader before doing this. It will flash the *.nbh file onto the device. When it is finished, it runs the format command from the .exe and formats the device. Once the percentage gets to 100%, it will hang for a moment while the task29 command is running. It takes about 10 seconds while it says 100% on the screen. During this time, hold down the voldown button until it reboots. Once you get back to the bootloader, go ahead and flash your next ROM.
Once you get the hang of it, the whole process shouldn't take you more than about 15 minutes or so. Setting everything back up after a flash is what is so time-consuming. Most ROMs come with some form of an auto-install program designed to install programs and import other data automatically. Read the thread of whichever ROM you choose before diving into it.
Don't ask us for our opinions on which ROM you get either. That's like asking which music you should listen to. Everyone likes different things. Just keep flashing ROMs until you find one you like. Otherwise, you can find hundreds of threads from other users asking "Which ROM should I choose" all over the forum.

Ok. sounds pretty easy, thank you for being so generous and as I was browsing I found a link with how to run the task 29 http://forum.xda-developers.com/showpost.php?p=5845908&postcount=1 from what i gather on this just sync and run the .exe file and that should take me to the bootloader screen? and the after its done run my .nbh file from my custom rom and should be the end besides setting up the rom? I've seen to many people ask which rom is best and seen the responses people have given them so I know better to ask lol. Thank you once again, I greatly appreciate it.

nitegmoney said:
Ok. sounds pretty easy, thank you for being so generous and as I was browsing I found a link with how to run the task 29 http://forum.xda-developers.com/showpost.php?p=5845908&postcount=1 from what i gather on this just sync and run the .exe file and that should take me to the bootloader screen? and the after its done run my .nbh file from my custom rom and should be the end besides setting up the rom? I've seen to many people ask which rom is best and seen the responses people have given them so I know better to ask lol. Thank you once again, I greatly appreciate it.
Click to expand...
Click to collapse
It sounds like you've got it. Just don't use the customromruu.exe file from the task29 to flash anything other than the nbh that comes with it. It will erase anything it flashes to the internal memory right after flashing it. Any other ruu.exe file is interchangeable for anything else, though.

I downloaded the task 29 zip folder and unzipped it and got a file "task 29 provided by doloop" take it that is what I'm suppose to use? One last question for you, on this sight how do you find the latest version of a rom?

nitegmoney said:
I downloaded the task 29 zip folder and unzipped it and got a file "task 29 provided by doloop" take it that is what I'm suppose to use? One last question for you, on this sight how do you find the latest version of a rom?
Click to expand...
Click to collapse
They must have changed the format of the task29 tool. Either that or I've got an older version. Mine's wrapped up nicely in one simple *.exe file. If you downloaded the *.zip from the first post of the task29 thread, then just double click on ROMUpdateUtility.exe to begin the process. Where did you download your file from? Provide a link so I can better answer your question.
The latest version of a ROM is normally on the first page somewhere. It varies by chef, however. Some put links as a reply in the thread, so it might be a ways back. Check the first page of posts first. If you don't find it there, ask on the thread. Be sure to read the rules and FAQs of the ROM before posting questions.
The best advice I can give you is to always search first before posting questions. Take the time to show other members that their time is no less valuable than your own, and most members will bend over backward to help you out. If you post without searching or doing work for yourself, it tells other members that your time means more than theirs, and you are more likely to get flamed rather than helped.

http://forum.xda-developers.com/showpost.php?p=5848003&postcount=19
this is the link where i dowloaded it from the in the very first box, you have really been such a great help, let me know if this is the right one thank you.

nitegmoney said:
http://forum.xda-developers.com/showpost.php?p=5848003&postcount=19
this is the link where i dowloaded it from the in the very first box, you have really been such a great help, let me know if this is the right one thank you.
Click to expand...
Click to collapse
Extract and drop the attached file into a folder with that *.exe, and you'll be all set. This file is basically just a tiny OS that it will flash before hand. As I said, once the process gets to 100%, it will hang there for about 10 seconds or so while it formats the memory. It will erase what this file writes anyway. I think the *.nbh from the first post is a HTC boot screen file. That will change the first boot screen you see when the device powers on and you see the red letters at the bottom left of the screen. I don't need to change my boot screen, so I use this one, since the task29 will wipe it out right after, leaving no trace of anything being flashed.

Thank you very much, quick question while your here, got my rom downloaded after the task 29 do i run the .nbh file or rhodium software upgrade? Can't say thanks enough

with the file you gave me after i extraxt with 7 zip it says windows cannot recognize this file? is it cause i have windows 7?

nitegmoney said:
with the file you gave me after i extraxt with 7 zip it says windows cannot recognize this file? is it cause i have windows 7?
Click to expand...
Click to collapse
You don't run that file. Put the *.exe into a folder with the*.nbh file I just gave you. You run then double click on the *.exe to begin the task29 process. The *.nbh is a required file. I don't know if it is included in the one you downloaded or not.
On second thought, here are the task29 file I use. Extract to a folder, run the *.exe, be happy, in that order.

Got it work with the two files custom ruu and the .nbh just click the custom ruu one and start from there? Sorry for being a birden.

nitegmoney said:
Got it work with the two files custom ruu and the .nbh just click the custom ruu one and start from there? Sorry for being a birden.
Click to expand...
Click to collapse
Make sure the device is connected via ActiveSync, or put it into bootloader and make sure it says USB at the bottom of the screen. After you confirm one of these two scenarios, run the*.exe. Once it gets to 100%, hold the voldown button and allow it to boot back into the bootloader. From there, wait for USB to show at the bottom, and begin flashing the new ROM. I honestly don't think I can make it clearer than this. I hope you get it working.

You've made it very simple i just got to the bootloader screen thank you, it says usb, but when i try to run the custum ruu nothing happens

nitegmoney said:
you've made it very easy and I do appreciate it very much... Only issue im having wen trying to enter bootloader mode it says it cannot be opened as it is not signed with a trusted certificate....?
Click to expand...
Click to collapse
I assume you meant the *.exe is giving you the message. Turn off antivirus software, and run the file as administrator.

[Update]Radio ROM Thread. (all 8 hd7 Radio's are online)

Here you find some radio rom's for your hd7
[Update] now you will find a custom wrapper made by Dave shaw" attached to this post.
and here a link to Dave Shaw his thread where he share his wrapper to the world
http://forum.xda-developers.com/showthread.php?p=16460826&posted=1#post16460826
task 00 - this does not perform any kind of format after flashing a ROM.
This is the one you should use when flashing just Splash screens or Radios.
It saves you from having to restore all your data.
what to do with this:
1) download the attachment and extract (HD7_RUUWrapper_00)
2) download a radio you want to flash and extract.
3) copy the RUU_Signed.nbh from the stock folder (only for now, will update later)
4) bring phone in bootloader.
5) run ROMUpdateUtility.exe
6) follow instructions on screen.
7) run R/H spl again (this will change later when I updated the radios)
how to bring phone into bootloader mode:
(reboot while hold volume down button pressed). Connect to PC and wait for drivers to be installed. (USB appears on the bottom of phone screen) Than start updater to flash radio.
if you have a rom with a radio that isn't in this post please send me a download link
in the .rar we have:
nb folder (here you find the spl.nb and radio.nb)
Stock folder ( here you find the stock spl/radio.nbh)
XML folder (here you find a .xml with all the data from the 2 .nb files)
RUU_Signed.nbh (this is a radio only .nbh)
O2_DE_3.04.207.01_Radio_5.66.09.21a.rar Online.
http://hotfile.com/dl/126051344/13bdd33/O2_DE_3.04.207.01_Radio.rar.html
HTC_Europe_1.60.401.01_Radio_5.52.09.16.rar Online.
http://hotfile.com/dl/126052660/7210f63/HTC_Europe_1.60.401.01_Radio.rar.html
TMOUS_3.01.531.02_Radio_5.65.09.25a.rar Online
http://hotfile.com/dl/126116342/0c7c824/TMOUS_3.01.531.02_Radio_5.65.09.25a.rar.html
TMOUS_2.20.841.02_Radio_5.65.09.11a.rar Online
http://hotfile.com/dl/126114473/3837310/TMOUS_2.20.841.02_Radio_5.65.09.11a.rar.html
HTC_Europe_1.54.401.01_Radio_5.51.09.29.rar Online
http://hotfile.com/dl/126109079/59069fc/HTC_Europe_1.54.401.01_Radio_5.51.09.29.rar.html
Telstra_WWE_3.04.206.01_Radio_5.66.09.21a.rar Online
http://hotfile.com/dl/126112664/091ef3e/Telstra_WWE_3.04.206.01_Radio_5.66.09.21a.rar.html
O2_UK_1.68.206.03_Radio_5.63.09.13_3a.rar Online
http://hotfile.com/dl/126202114/5e48ff0/O2_UK_1.68.206.03_Radio_5.63.09.13_3a.rar.html
Telstra_WWE_1.50.841.02_Radio_5.61.09.15a.rar Online
http://hotfile.com/dl/126205305/0aa2586/Telstra_WWE_1.50.841.02_Radio_5.61.09.15a.rar.html
Remember you have R/H spl by Cotulla.
Remember that this will NOT reset the phone
Remember that if you take the radio from the stock folder that this will undo R/H spl so you have to run that again to
Thanks goes to:
Dave Shaw for making us a wrapper that doesn't hard reset.
xboxmod for helping me with almost everything
ondraster for the good chats (most things I really didn't understand )

updated the first post
I updated the first post with a ROMUpdateUtility.exe so that all can easy flash the radios to the phone

Thanks a lot for these Ceesheim. Wish I would've had these before I rolled all the way back to catch the firmware update from Tmob By the way, if we flash the new radio from Tmob, will it update all firmware that is in the actual update? I'm asking as I need to do a friends phone and would like to avoid rolling back just to get that done. Lastly, (and this is just to be sure), but will the phone really be hard reset from just flashing the radio (unlike it used to be on WM).

kwill said:
Thanks a lot for these Ceesheim. Wish I would've had these before I rolled all the way back to catch the firmware update from Tmob By the way, if we flash the new radio from Tmob, will it update all firmware that is in the actual update? I'm asking as I need to do a friends phone and would like to avoid rolling back just to get that done. Lastly, (and this is just to be sure), but will the phone really be hard reset from just flashing the radio (unlike it used to be on WM).
Click to expand...
Click to collapse
first
yes sorry , for now this will Hreset the phone because there is no public custom wrapper (one that does the task 32 instead of task 28)
"By the way, if we flash the new radio from Tmob, will it update all firmware that is in the actual update?"
do you mean a os update by ZUNE/MS/HTC ?
sorry don't know actually what you mean by this ?
but what this does is only updating the radio rom ( not the os and not the spl)

ceesheim said:
first
yes sorry , for now this will Hreset the phone because there is no public custom wrapper (one that does the task 32 instead of task 28)
"By the way, if we flash the new radio from Tmob, will it update all firmware that is in the actual update?"
do you mean a os update by ZUNE/MS/HTC ?
sorry don't know actually what you mean by this ?
but what this does is only updating the radio rom ( not the os and not the spl)
Click to expand...
Click to collapse
Ok, just wanted to be sure about the hard reset. And I mean there was an update from Tmob talked about here http://forum.xda-developers.com/showthread.php?t=1188563 and wanted to know, if you install the radio which comes from this firmware update, will all the components of the firmware be updated as well? Or is the firmware update, pretty much just an update to radio and that's it?

kwill said:
Ok, just wanted to be sure about the hard reset. And I mean there was an update from Tmob talked about here http://forum.xda-developers.com/showthread.php?t=1188563 and wanted to know, if you install the radio which comes from this firmware update, will all the components of the firmware be updated as well? Or is the firmware update, pretty much just an update to radio and that's it?
Click to expand...
Click to collapse
it will only change this "5.51.09.11a" to "5.65.09.25a_22.45.50.21U." part
or one you like
and if you look at the phone (on custom dft) you will see this 2250.21.30401.531.DFT
the number 2250.21.30401.531.DFT is just an identification number I think, it doesn't say anything about with build you have.
so if you ask me then if you only update the radio all would be ok.
edit:
lol, yes to me it looks like just a radio update, and you can take every radio you like my radio comes from this "http://forum.xda-developers.com/showthread.php?t=1183891" rom (I extracted it and removed the spl)

So im right in thinking the new custom RUU won't hard reset the device when flashing radios?.
Cheers kev

sutt359 said:
So im right in thinking the new custom RUU won't hard reset the device when flashing radios?.
Cheers kev
Click to expand...
Click to collapse
yes I am testing one as we speak but the problem is that it generate errors (and that isn't good for noobs )
and I can also tell you that the custom ruu is actually worked (no hard reset after radio flash )
but first the errors need to be fixed after that it will be posted on xda

i am trying to flash this "TMOUS_3.01.531.02_Radio_5.65.09.25a" on my HTC HD7 Tmobile.i am getting error 270 - update error
This is my phones Radio 5.54.09.21._22.33b.50.10U . I am not able to download through marketplace so i want to try different radio.
Im on CotullaHSPL 3.1

sagarjawaress said:
i am trying to flash this "TMOUS_3.01.531.02_Radio_5.65.09.25a" on my HTC HD7 Tmobile.i am getting error 270 - update error
Click to expand...
Click to collapse
when flash is at 100% then just remove batt
if it didn't update then use the radio in the stock folder and run r/h spl after flash one moer time .

ceesheim said:
it will only change this "5.51.09.11a" to "5.65.09.25a_22.45.50.21U." part
or one you like
and if you look at the phone (on custom dft) you will see this 2250.21.30401.531.DFT
the number 2250.21.30401.531.DFT is just an identification number I think, it doesn't say anything about with build you have.
so if you ask me then if you only update the radio all would be ok.
edit:
lol, yes to me it looks like just a radio update, and you can take every radio you like my radio comes from this "http://forum.xda-developers.com/showthread.php?t=1183891" rom (I extracted it and removed the spl)
Click to expand...
Click to collapse
Ok, got you. I'm sure there has to be something else in the firmware update besides the radio, but probably doesn't matter much anyways. Can't wait for the custom wrapper either

kwill said:
Ok, got you. I'm sure there has to be something else in the firmware update besides the radio, but probably doesn't matter much anyways. Can't wait for the custom wrapper either
Click to expand...
Click to collapse
hey Kwill , look at first post

The TMOUS update you're talking about included driver updates to fix the HTC Pink Camera issue. So, flashing just a radio ROM from here will not help. Flashing a custom ROM may undo this as well as I don't know if the custom ROM's have the updated drivers.

Expriences
Hi!
I was just wondering if I flash the RUU_signed.nbh from the root folder the Cotulla HSPL remains in place. Which is really true but the phone cannot start: it keeps returning back to the BootLoader.
This is easy to resolve: Flash RUU_signed.nbh from stock folder of the archive as it is described in the first post. Cotulla HSPL is gone but ROM and data is intact. .
Hope there will be a fix for keeping HSPL in place.
Anyway this is far more easy now to upgrade my radio. I thanked every post by ceesheim here. (I hope I won't get in to trouble with that. )
Really thank you guys.
Cina.

As seen in many Android XDA forums with modem, this thread is stuck now.
Btw, nice job , a well made thread, i've found it so understandable.

ceesheim said:
hey Kwill , look at first post
Click to expand...
Click to collapse
Aha! Thanks ceesheim and definitely thanks to Dave for the custom wrapper!
drkfngthdragnlrd said:
The TMOUS update you're talking about included driver updates to fix the HTC Pink Camera issue. So, flashing just a radio ROM from here will not help. Flashing a custom ROM may undo this as well as I don't know if the custom ROM's have the updated drivers.
Click to expand...
Click to collapse
Ok, that's what I was afraid of (there being something that wouldn't update with the firmware update). Guess I'll take my friends phone through the rollback and update him that way. Thanks drkfngthdragnlrd for chiming in on that one.

cina said:
Hi!
I was just wondering if I flash the RUU_signed.nbh from the root folder the Cotulla HSPL remains in place. Which is really true but the phone cannot start: it keeps returning back to the BootLoader.
This is easy to resolve: Flash RUU_signed.nbh from stock folder of the archive as it is described in the first post. Cotulla HSPL is gone but ROM and data is intact. .
Hope there will be a fix for keeping HSPL in place.
Anyway this is far more easy now to upgrade my radio. I thanked every post by ceesheim here. (I hope I won't get in to trouble with that. )
Really thank you guys.
Cina.
Click to expand...
Click to collapse
Where is the stock folder of the archive which contain RUU_signed.nbh located.I need to deinstall my HSPL.

Hi, I've read the instructions a few times, but I guess I'm missing something. I keep getting the attached Error when I run it. My phone does the have the HSPL also.
Thanks

i am on asia HD7 Singtel
i would suggest not flashing this thing onto yr phone because a while back i recenived the same HTC firmware update available to Tmous users.
the htc update updates the radio to 5.65. and we arent sure if it contains other enahncements, bug elimination or any other improvements

Ttblondey said:
Where is the stock folder of the archive which contain RUU_signed.nbh located.I need to deinstall my HSPL.
Click to expand...
Click to collapse
You should download any Radio ROM archive from the first post than extract it. Inside you can find three folders. Or of them (stock) contains RUU_signed.nbh you're searching for. Use that for flashing.
Sent from my HD7 T9292 using XDA Windows Phone 7 App