yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Tectronus:
I found and used this today to see if it would help with issues i was having. I was installing a custom rom today and even after the flash dance was having lock ups while the rom was setting up after the flash. No others where having problems with this rom so i gave this tool a go. Used this and reflashed the rom... Installed with out a hitch after..

Thx for the tool and i hope others will have positive results after as well..
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Lyresti:
Thanks

Agent_47, just wanted to say thanks for Task 29. So easy to use and get a nice, clean device to start with.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] 4bettilt2:
Question for newb

Is it necessary to remove battery if planning to flash rom and radio via usb after running task 29???
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] GbNoR:
Tried it on Touch Pro (Raphael)

Hey Agent 47

I tried it on a Raphael, and it seems to work great.

Replaced the ruu_signed.nbh file, with my preferred radio (1.14.25.35) file.

After running ROMUpdateUtility.exe, my device booted up, and got stuck on bootscreen (just showing the Touch Pro image).

I then entered bootloader, and flashed Energy Series (23554/21898) ★ |Mar 30| Sense 2.5 !, for TP. :D
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] SacTilt:
For my TP2, I'm doing the following with success:

Connect to PC via Active Sync/WMDC.

Execute Tool 29.

When phone boots to "Touch Pro 2" screen, I hold down the volume down button while hitting the reset button.

Once I'm on the Bootloader screen, and it shows "USB", I flash the new ROM from the PC as I normally would.

When the phone vibrates, indicating the ROM upgrade is complete, I disconnect the phone from the computer.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] blast0id:
Well then, I'm going to get crazy and try it for Fuze... hmmm... maybe someone who has recently upgraded to a TP2 or HD2 could send me their old Fuze/TP if I brick this in the name of "science" ??? hehe... not holding my breath on that... but if you do have one (old working Fuze/TP (GSM)) I wouldn't mind the "security blanket" hehe =)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] MCbrian:
This is exactly the way I did it, too.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] agent_47:
u r one brave man!
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] blast0id:
Well, I tested and it worked for my Fuze/RAPH110... thanks!
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] ziggy471:
Well, I finally said what the hell, and tried it, it does work. As for you not being able to run it, there are more files that are needed other than just the RUU exe to run. I've attached the full blown RUU package if you want to take a look.

Again, thanks for all the hard work Agent_47, we appreciate it.

Z
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] agent_47:
thnx for confirming, opened a thread in CDMA section..n thnx for filling in the missing files :)

http://xdaforums.com/showthread.php?p=6053250#post6053250
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Stivenson:
I just wanted to try task29. It didn't work for me.

I downloaded the file Task29 provided by doloop.exe from the first post. My TP2 was synced with my Windows 7 32bit.

I run Task29 provided by doloop.exe, my phone went into bootloader and 'flashing' started. But as the progress bar went to 19% i got ERROR 244 on the computer (see attachment). Then my phone rebooted itself and my old ROM was still there. I can still use my phone without any problems. But the question is: why i get this error?

Any ideas?`

10x in advance.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Stivenson:
Ok, i read the instructions in Post 1 one more time.

i must extract Task29 provided by doloop.exe

But if i do this, there is no ROMUpdateUtility.exe but only a ROMUpdateUtility.cfg

Or should i use the ROMUpdateUtility.exe from the HTC stock ROM?

Please help...
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] SacTilt:
You need to download the task29.zip file from the first post, and then unzip it, and use that. That will contain everything that you need.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Stivenson:
You can all call me an idiot! :)

I don't know where did i get thie Task29 provided by doloop.exe file from...

I just downloaded http://valkyrie.htc-files.com/downloads/roms/valkyrie/rhodium/task29.zip and did everything like it is explained in the first post -> Everything worked fine!

Thank you for this nice tool :)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] mwalt2:
There's nothing specific to Rhodium besides the radio is there? It seems like this would work for all HTC devices if you used the device-appropriate radio. I'll try before I flash my diamond next, but would like confirmation just in case :). Good work agent_47.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] agent_47:
in theory it should work.....but i m a simple guy who don like risks except when it comes to poker :p
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] frycook15:
worked great for me as i have flashed lots of roms went of without a hitch
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] mwalt2:
heh, I'll keep you updated when I try :).
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] richabi:
But the user said he flashed a custom ROM afterwards. Shouldn't that ROM splash image overwrite the stock splash he had regardless if task 29 was used or not?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] MCbrian:
I think it depends... I flashed to the stock T-Mo WM6.5 for about a day, then went back to a Valky rom, and the T-Mo "Stick Together" splash screen persisted through several custom rom flashes. Then it went away...

I've seen a cook explain why, but don't remember exactly.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] blast0id:
well, I used it on my fuze with no problem, and another user has used it on his Touch Pro without an issue... so I think you would be pretty safe in trying it...

obviously the OP/creator has to err on the side of caution when suggesting whether or not you should try it... =)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] 4bettilt2:
Finally ran it

Hi ran task 29 after unzipping the download by clicking on ROMUpdateUtility from the unzipped folder seemed to go well although when I went into bootloader mode afterwards it showed my previous radio??? well anyway then loaded my rom and things seem fine but I guess this wasn't a total reformat.

what did I do wrong?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] blast0id:
it only wipes the ROM area of the memory... as far as I am aware...
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Reefermattness:
yup, only ROM, he states that HSPL and Radio stay.

Works amazing by the way. Cheers!
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] steviewevie:
I used this today. Was slightly nervous, not having tried it before, but no need - it works perfectly, very easy. And as has been said, it doesn't touch the radio.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Achelos:
Can anyone mirror the file for me? htc-files is offline for me, can't even get it through not using my dns, by using opendns or several webproxy's.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] momoclax:
I can't download it too... , mirror please
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] abbas:
After doing task 29, I got an SOD about an hour after installing Cell Evo April 1 build.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] 4D3:
Hi,

im using win 7 x64 and this does not work at all. no matter what i do i cannot get this to connect, i just get "Error 260 COnnection"

have run as admin, have removed all mtty drivers rebooted my system.

this thing does not work for me, someone explain how.

At the OP:

UNTRUE - you should state that this doesnt work on x64 based systems without installing extra drivers, or provide a guide that works for x64.

the title of the thread is VERY misleading!

MG
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] SacTilt:
Works perfectly fine for me on Win 7 x64. Not sure what your issue is, but I can confirm that it DOES WORK on x64.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] SacTilt:
An SOD has nothing to do with Task 29... which has been stated a few times in this thread.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Maxx134:
Thank you so much!

This beats me having to perform a "clear storage" like a fool with both hands pressing buttons and stylus in my mouth for reset hole :p
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] MCbrian:
I also can confirm that this runs/works fine from W7 x64 -- I've done it twice.

Please don't blame the creator of this very usefull tool for a problem that lies with your computer or your TP2.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] 4D3:
what drivers? I cant get it to work without F8 on mtty drivers.

MG
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] twopumpchump:
i just installed a fresh copy of win7 x64 last weekend, and this tool ran on win7 out of the box.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] chadster214:
aGPS

anybody having problem connecting to aGPS after flashing to Task29?? it seems flashing to Task29 breaks the aGPS..
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] SacTilt:
No special drivers. Never even used mtty. Just downloaded this and ran it.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] SacTilt:
No problems here.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] blast0id:
I doubt that is even possible...
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] chadster214:
how are you guys testing the aGPS?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] rifraf1:
I notice most comments refer to flashing via usb, I presume since you are already connected by usb, but I prefer to flash from the mSD card. Having read the entire thread I noticed one person say he lost the ability to flash from the mSD. This will not alter your phone so you lose that capability will it? Flashing from either usb or mSD is still going to be an option after running this correct?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] steviewevie:
Fine for me. All Task29 does is wipe out the ROM. If you're having problems with aGPS then I would check your ROM itself, your radio version and perhaps even your hardware.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] SacTilt:
TomTom

Google Maps

Bing
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] SacTilt:
That's correct.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] agent_47:
title is fine mate!

works out of the box... 2000+ post to ur name, i would expect u to no wat error 260 connection means.....:eek:

anyhow, atleast check what other users have posted over the 1st 5 pages before posting such a rude post without doing ur homework

peace!

no reason for it not to work :p

checked ur settings.....refer to ur rom thread for details and confirmation of the problem not related to the rom :)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] rohithathie:
does this need HARDSPL?????

i don't want to hard spl my phone..
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jhernand1102:
Yes you need hardspl..
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] shiftylock:
I must say, you are a genius for this!

Worked 100%, and my rhodium is thankful :)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Henz77:
ehm i am using official ROM, so its ok if i hardspled it? coz w/o hard spl, the upgrade only stated 0% an after 5 mins it said error bla bla bla.

reason i still use official rom is becoz i need to input asian language ( chinese ) on my TP II. if any cooked with ALS ( chinese input ) i dun mind to upgrade >.<

regards
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] steviewevie:
You can still use official ROMs even if you have HardSPL.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jhernand1102:
Yes you can still install hardspl if you want and use the official ROM but my question is if your using the official ROM then why do you need to used this utility? This is for people that flash different ROM's all the time. It helps clean up any left over fragments from flashing different ROM's so unless your planning on flashing cooked ROM's then you really don't need to use this utility...:)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] DebbieNY13:
I've lost the ability to connect via USB (been syncing via BT USB), however, I will keep a watch on this thread in case I get rich enough to fix it, or someday this works via mSD card. :D

Thanks for this!

Debbie
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Henz77:
well i re-flashed my ROM sometimes with the same official ROM, reflashing it with the same ROM sometimes needed to removed the unwanted errors or somethings like it. i re-flashed with official ROM several times, but i see that some registry n setting still not removed n still there.i want to completely removed the reg n any other things to really get the brand new official ROM without any error from the previous ROM.

thats why >.<

so if i hard spl my TP2, i still can use official ROM right?

but if i want to take it to the service center, returning to actual SPL only for warranty correct?

thanx >.<

regards
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jhernand1102:
Yes you can use the official ROM after using hardspl and yes you must relock using the files and procedure in the hardspl thread before you return for any warranty service...good luck...:)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Henz77:
wow i'd just finished flashing it. n guess wat i get 0.o?

i use SEA official ROM, usually i only got 160mb space to install program, after using this task 29, now i got 201mb space to instal program 0.o, wow significant 40m space n its a wow 0.o

thanx a lot for providing me answer n help n also thanx for making this thread n sharing.

i appreciate it greatly.

best regards thanx >.<
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] fmedrano1977:
Is this a Rhodium only tool?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] JonDeutsch:
before I use this tool for the first time, I have a basic question:

After I use task39, there will be no bootable phone. In that case, since I always flash my new ROMs via USB/Mobile Device Center, does that mean I can no longer flash using this approach? How would I get the phone to see USB connection if there's no ROM?

I've never flashed from microSD before, so that would be something new for me to figure out if that was required.

Any info appreciated.

Thx.

Jon
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] MCbrian:
No, USB/MDC flashing still works fine after Task 29. There's no os-rom, but not everything on the phone has been deleted. (It's like it's in "persistent vegetative state", not quite brain-dead :D. )

When Task 29 has done its thing and it's "stalled" on the "Touch Pro2" screen, just press on the down-volume key and poke the reset-hole simultaneously and that will put it into bootloader. In a couple of seconds the PC should see it as a USB device and "USB" will appear at the bottom of the TP2 screen -- ready to flash.

BTW: You don't need to pull the battery out if you follow the procedure I give above to go directly to bootloader.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jhernand1102:
Once you use task 29 when its done pull the battery out..plug your phone to your computer, put the battery back in and then hold the volume down while pressing the power on button..the phone will boot in to the bootloader mode and it should detect the usb connection...then you can just flash away
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Firethorn:
I'm at this same junction, but my pc (XP) is not finding my phone. What can I do?

Clarification: I too ran task29 and now I'm sitting at bootloader..phone says USB at the bottom, but pc finds nothing.

Solved: Evidentally it is recognized in XP without XP giving any indication that it is recognized..I have no idea, but I was able to install my rom.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] theguy0075:
I've been hesitant to try this out as I don't encounter too many bugs and have never had an SOD incident (must've gotten lucky and gotten a Wednesday phone), but anything that might make my device run smoother or more optimally is worth a try. I must say that, both the time it took to read the entire thread and the extra time this adds to the flashing process (placing NBH on mSD, removing mSD and sim, running task29, replacing mSD, flashing from mSD, replacing sim, first boot and customization, hardreset, second boot and customization, not to mention flashing stock ROM which I havn't done in a while) leaves a bad taste in my mouth. I feel like this process may be able to be streamlined a little but I'm not well informed enough to know whether some of these steps are redundant and can be skipped. If anybody who knows better than me and can provide a better/simpler description of what should be done between flashes, both for those whom prefer to flash via USB as well as those whom prefer the mSD method(me), this would help a great deal more users than just me.

I greatly appreciate all the work done by the developers to create these kinds of tools along with awesome ROMs, but that dedication and attention to detail doesn't seem to find its way into things like step by step instruction. This is not meant as a slight towards Agent47 at all but I feel like most users don't have the patience I do when it comes to reading threads in order to get things right the first time. Instead they quickly read the first post and maybe the next few and end up doing something wrong which creates the situation we have here, a thread with unclear instructions and far too many useless replies. This is a thread that should contain DETAILED instructions in the first post and gads of replies of nothing but praise for a splendid tool.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Lennyz1988:
Just place the .nbh on you're sd card. Take you're sd card out. You don't need to take out the sim when flashing from you're SD card. I never do and I have flashed alot. Run task29. Then put you're sd card in and flash. When flashing is done, reboot. You don't have to wait for the customization to hard reset and I don't think you even have to hard reset when you have run task29.

And I don't know why you want to install the stock rom from time to time. I never did and I never have strange issues. Maybe this post will help you a little :)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] MCbrian:
Just do what it says in Post #1 -- where it says "Instructions:" -- that's it. Well...actually, Post #1 does neglect to explicitly say that the tool is unzipped to your PC and the phone is connected to a PC via Activesync during the process -- but that's it. There is no more detail required because there are no more steps required. Anything else is not part of Task 29.

I agree that if you did all of those things that you list -- that would be a lot... but almost none of those steps have anything to do with running Task 29.

Multiple hard-resets (??) and flashing stock roms (??) is definitely

not

part of Task 29. :confused:

Maybe you got confused because of Post#22? Well ignore that post -- it's just a description of what one guy does to run Task 29 AND flash a rom. The Task 29 instructions end with Step 3 (and it's not even necessary to remove sim and sd card).

I don't do this every time I flash, but when I do it adds less than 2 minutes to the rom-flashing process. :)

(see my Post#147 for why/how you don't even need to remove the battery to put the phone into bootloader mode)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] moopile:
I remove my SIM during flashing for a couple of reasons. Incoming call or text during installation has caused errors. If my SIM is in, my emails will start and save to Device before I have a chance to set them to Storage Card.

@theguy0075, I don't flash back to stock when using Task29. Task29 replaces that step and is much faster (few seconds compared to several minutes.) When Task29 is complete, power off, insert microSD, power on into Bootloader to flash ROM, Hard Reset (may not be necessary, but if everyone did it, it would make trobleshooting bugs in cooked ROM's easier), Make some changes on phone, insert SIM, run carrier provisions.

For the record, you can still flash ROM over USB, but I never do. Often, I have to leave the office while phone is still flashing, so mSD version works best for me.

So, I believe that Flashing Stock or Task29 before installing a cooked ROM and then at least one Hard Reset and finally installing SIM, provisioning, soft-reset are necessary steps to being a "good citizen" on Chef's threads. Those who follow these steps seem to not experience small to major glitches that others do, thus streamlining the troubleshooting process for Chef errors.

Goodluck!
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] agent_47:
i don see a need for a detailed post.....becoz

1. the steps u have in bracket are either not required or will defeat the purpose of the tool.

2. this tool is effective if your flashing a lot, so i would asume u know things like how to flash a rom and connection error 260

pardon me if i assume too much....but i always have been like this :o
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Powpow24:
Hi, i just installed the task29 and ran ROM Update Utility

i waited for it to finish and i am now on the reboot screen.

now, i open the CustomRUU and it says that "The Update Utility can not open the requested file. Please check Your Update Utility."

Usually when i flash a new Rom it doesn't say that.....

this is my first time using task29 and i'm stuck... can anyone please help? thanks in advance :)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] MCbrian:
Are you trying to flash a rom that you've flashed before -- one that you're sure works?

And the rom file is called "ruu_signed.nbh" and is in the same folder as CustomRUU.exe?

The last time that I got that error message there was an error in the rom file, the .nbh file -- that's "the requested file" that can't be opened.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Powpow24:
well, i havn't tried it before, so im not really sure if it works

and yep, the file is ruu_signed.nbh and is in the same folder as CustomRUU.exe

hmmm..... should i try the mSD method?

EDIT: wait, im trying to download the ROM again to double check that the CustomRUU that i tried running is IN the same folder and not the one that i've downloaded and saved before during my last flash (idk if that made sense..)

EDIT: Yup, that's what i did wrong. i guess it wasn't the CustomRUU.exe wasn't in the same folder as the ROM. hehe thanks MCbrian for bringing that up! ^^
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] rjmjr69:
I assume this is safe for any htc device? CDMA included?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] MCbrian:
Maybe not... I think the author advised against it. Might be worthwhile to search the thread for "CDMA", if you haven't already.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] GaryMcQ:
Task 29 for CDMA

Here's a link to a CDMA version created by Agent_47 and modified by Ziggy. Go down to post #9 to get the Task29.exe that Ziggy modified for easier use.

http://forum.ppcgeeks.com/showthread.php?p=1673997&highlight=task29.exe#post1673997