yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] Logicalstep:
Thats what I was thinking when reading this thread... allot of you saying that you managed it successfully, but not many posting about if it has actually made any difference to the performance of your device.

Is this worth doing? does it make a noticeable difference in the performance of Custom ROMS?

Many thanks for all efforts by Devs here to make things better :D

Logicalstep
[Touch HD Windows Mobile ROM Development] jigners:
a summary of how useful Task 29 has been to the above members of this forum

Pandemoniumone has 2,385 posts in this forum!
[Touch HD Windows Mobile ROM Development] ferraridave:
You had a power cut during a flash and recovered from it.

Can you guarantee that everyone this happens to will always recover their phone successfuly ?

I flash from SD as much as possible because it takes power cuts completely out of the equation, and therefore removes a risk of bricking.

So when flashing from SD instead of from you're PC without a UPS as I always advise, can I guarantee that the phone being flashed will not become a brick because of a mains electricity power cut ?

Yes indeed I can !

So I think I'll stick with the flashing from SD method thank's.
[Touch HD Windows Mobile ROM Development] jimk68:
Agree with ClydeB1, at bootloader your PC is just a extension like an SD card. At bootloader it just waiting for you to load from com or sd.

Cheers
[Touch HD Windows Mobile ROM Development] kaushama:
How do we know it formats the internal memory for sure? Does it just install radio?

I am a multi flasher and using most recent Topix ROM. Earlier I used to flash the stock ROM and then the new ROM. If it formats the drive this is going to be the best way of flashing new custom Roms.
[Touch HD Windows Mobile ROM Development] jrmccann:
Thanks Jigners for your "a summary of how useful Task 29 has been to the above members of this forum"...that helps a lot!!

Now I should read up on how you do it!! You all make it sound so easy, but...

Regards

J
[Touch HD Windows Mobile ROM Development] jimk68:
This thread already self answer and read post 1
[Touch HD Windows Mobile ROM Development] first_damned:
Task 29

Brilliant, worked fine for me on windows 7 32bit, using radio 1.17..

alot faster than flashing a stock rom!
[Touch HD Windows Mobile ROM Development] ferraridave:
Perhaps I need to explain it bettter for you, from your above statement you are saying that both methods of flashing are equal, yes ?

Wrong, by flashing from your computer, you are adding that computer and the mains electricity supply that powers it into the process, and you can't tell me that your computer and your electricity supply are 100% reliable, to think that no component inside your pc will ever fail, or that you will never have a power cut is just sheer stupidity.

My PC is extremely reliable, but to think it is 100% reliable, will never crash, or will never have a component break would be extremely foolish of me.
[Touch HD Windows Mobile ROM Development] lelo4ever:
sorry but you are wrong...

the worst thing that can happen if a powercut happens is that you'll need to start all over again flashing through bootloader... that's it...

the main difference about flashing through SD card is speed... is a little faster... but usually is not enough to make a big difference...

i can tell you that i have experience on that matter... Due to the fact that I'm an USPL User... By mistake i've started flashing before injecting USPL properly a couple times... and by doing this i NEED to stop the flashing process in the middle(after all it won't finish by itself)... usually i do it by soft reseting the phone... so if a powercut was a brick matter... imagine reseting the phone in the middle of the flashing...

to be honest... i don't like flashing through the SD card... my card is not that reliable... i've had problems a couple times regarding file corruption through heavy use... so i only use it for my GPS app and my mp3s and videos... I have 'em backed up if my card screw up...
[Touch HD Windows Mobile ROM Development] tin2404:
I think this thread should be sticky due to impact on every ROM performance and its efficiency is confirmed so far. Do you agree ?:cool:
[Touch HD Windows Mobile ROM Development] jigners:
its usefulness is confirmed and the thread may need monitoring as a few members finds the procedure daunting and or confusing and may need assistance. I'll leave it to FallenSpartan to decide.
[Touch HD Windows Mobile ROM Development] jimk68:
We are here to share and we share our experience on this thread what we went through with our HD.

Your point is taken and you can says you prefer SD method and your experience instead of dress down other member view (with words: sheer stupidity, extremely foolish)

Share and peace
[Touch HD Windows Mobile ROM Development] ferraridave:
I apologize for those harsh words, but I also speak from experience, firstly although partly unrelated, a few years ago now a good friend of mine bricked an old nokia, through disconnecting when he thought the flash was finished and it wasn't, and secondly although my blackstone obviously survived, I have had one bad flash with it, not long after I had got it I was flashing for a 3rd or 4th time and it never finished, left it for about 15 minutes and it just wouldn't finish, froze at 100%, didn't show update success, so I disconnected from pc and it took about another 5 minutes before it would startup, thought it had become a brick after less than 2 weeks, so ever since then I've only flashed from SD until Task29 came along, and never had any other problems.

So if I offended anyone then please forgive me, I like to eliminate as many risks as possible, and was just trying to get my point across.
[Touch HD Windows Mobile ROM Development] jimk68:
Thanks my friend for the nice reply. The credit should go to jigners, he was the one to show the way. For info I forget to go to bootloader, three times, task 29 through pc (laptop, imagine sh.. brick) It turn out faster.

1. Task 29 with radio 10~15 sec through usb

2. At 100% task 29 press volume down button, tri colour appear (credit cydeb1)

3. Flash your prefer rom through usb

4. No HR, good as new

Cheers my way
[Touch HD Windows Mobile ROM Development] r_9:
Agree that this thread should goto sticky! Useful tool for all users!!
[Touch HD Windows Mobile ROM Development] jigners:
the role i took was to take the risk of bricking my blackstone by threading in

uncharted/unfamiliar grounds which fortunately lead to something useful for the

community. CREDIT goes to doloop in HD2 thread for hex editing Task 29

which enabled it to run without MTTY.
[Touch HD Windows Mobile ROM Development] pizzaman79:
I can confirm that Task 29 also works with USPL on Windows 7 32bit without any problems. Didn't need to use tin 2404's version. Didn't need compatibility mode.
[Touch HD Windows Mobile ROM Development] ultravox:
Confirmed working. HSPL,XP,and SD flash. Thx
[Touch HD Windows Mobile ROM Development] jigners:
keep the good input going!
[Touch HD Windows Mobile ROM Development] MJRL:
You could have also problems in your sd card, they also die... :)

I flash with my laptop in battery mode :D, but i know if i have a crash in windows could brick my phone.

;)

I'm waiting for Xanny to release a new rom to try this...
[Touch HD Windows Mobile ROM Development] jigners:
give us your experience after mate:)
[Touch HD Windows Mobile ROM Development] fwt:
WOW :eek:

worked great here! :D

Win XP SP3

Task29 with Blackstone Radio

and now on a German ROM (latest FlexROM)

Great ... I love it!!!

thanks JIGNERS and all the REST

I Love this Community!!

:D:D:D
[Touch HD Windows Mobile ROM Development] bucksbunny:
Old drivers

Hello all.

I am also frequently flashing my Blackstone and during reading this thread decided tot try it. I also ran into the problem that with W7 there is an "Invalid ID" error.

Instead of reading the entire thread first (should have because solution is there...:() I DID roll back my windows drivers as was suggested. Problem is that now Windows now does not connect to my phone while in bootloader, even though I restarted my computer with the option "do not check certificate" (or something.

Anyone know how to reinstall my old (and therefore newer) driver?
[Touch HD Windows Mobile ROM Development] tin2404:
Well, my friend,It seems that you rendered your device...but, you should try this..There is a way to try but now read carefully ;) :

FIRST STEP - FLASHING RADIO

1. power of device,remove the battery

2. find a way from another device to copy your ROM and RADIO nbh file to your SD Card

3. FIRST rename RADIO on SD card to "BLACIMG.nbh" (without quotes!)

4. put the SD Cart in slot and turn on device while holding VOL DOWN

5. flash your RADIO

6. remove battery from device

SECOND STEP - FLASHING ROM

1. now remove SD Card again and battery from device

2. DELETE from another device BLACIMG.nbh file (radio file) and rename YOUR new ROM file to BLACIMG.nbh

4. put SD Card into slot and put the baterry and turn on device while holding VOL DOWN

5. flash your device with ROM

THIRD STEP - ON COMPUTER

Delete Windows mobile center synchronized files and uninstall Windows mobile Center...

Restart computer...

Instal Windows mobile center again.

In the moment while your device boot ROM, connect it to computer from a scratch and drivers will be installed again.

and just for notification...use SEARCH FORUM TOOL ! ;)

.
[Touch HD Windows Mobile ROM Development] MJRL:
In Windows 7 its recomended to start windows with F8, then choose disable driver signature to flash or even to install the old driver, thats how i do it everytime i need to flash.

Edit: When will this thread be sticky? ;)
[Touch HD Windows Mobile ROM Development] x8rui:
back to spl1.54 for warranty proposes

Hi all,

task29 it's great tool but i'm in doubt about to use it.

My doubt is about the warranty...you say that task29 don't touch on the spl files...so can i go back to the stock spl after use task29 if i need to use the warranty?

my blackstone had HSPL 1.56 Olinex.

thanks to all
[Touch HD Windows Mobile ROM Development] core7x:
yeah. work fine and feel the fresh ROM inside.. no junk file... just feel it.. dunno what happen background it . :P
[Touch HD Windows Mobile ROM Development] jigners:
Task 29 does not touch the spl version, if you notice on the video, right after running task 29 is battery out then bootlader, you still see HSPL Olinex.
[Touch HD Windows Mobile ROM Development] pizzaman79:
...or USPL (at least under Windows 7 32bit)
[Touch HD Windows Mobile ROM Development] xsight3:
also did a successful reset using Win7 32bit and using tin2404's method

and indeed.. device feels like new :P

thanks you guys!
[Touch HD Windows Mobile ROM Development] Shoarma1998:
Jigners,

Thanks for this solution! If only we had this solution a year ago, the xda forum would have 80% less posts... ;)

Thanks again mate!

cheers
[Touch HD Windows Mobile ROM Development] jigners:
funny enough i only rarely visit my Blackstone now a days as my partner is now

its new proud owner. LOL, now I got two devices to feed my flashaholicism.
[Touch HD Windows Mobile ROM Development] bucksbunny:
Will try that now. I believe it is only step 3 as my phone is still working otherwise...Will let you know if it worked.

Thanks in advance!

Bucks
[Touch HD Windows Mobile ROM Development] Maarten_0031:
Did a task 29 yesterday and the result really surprised me! The rom is much smoother with the same amount of free ram. It's amazing!

One question (to which I think the answer is yes): Is it advised to do a task 29 for every flash? Seeing that i'm a Frequent Flasher...
[Touch HD Windows Mobile ROM Development] x8rui:
back to spl1.54 for warranty proposes

So it's possible to back to stock spl for warranty proposes...rigth?

i'm trying to have 100% sure of this because i saw the video and for HD2 said, at 41seconds, that they can't revert back for their 1.42 spl after use task29...and i would like to use it...but i've 1 year and 8 month of warranty in my blackstone... so if isn't possible to revert back to stock spl if i need warranty assistence, i won't use task29.

thanks
[Touch HD Windows Mobile ROM Development] bucksbunny:
Rolling back drivers in Windows

Hello all.

Luckily fixed the problem with the drivers. Had to reinstall mobile device center.

After that, justy used a radio file with task 29 and no problems at all. :o

Flashing now, very anxious to see if I will notice any improvements.

Bucks
[Touch HD Windows Mobile ROM Development] Jayedamina:
i just tried task29 on windows 7 x64 i followed the directions posted...now when i try flash a new after its stuck at 35% (Error 226) 'FLASH write error happened'. i tried a few different roms and no change. please help!!:(
[Touch HD Windows Mobile ROM Development] MJRL:
Even if not, every stock rom will restore your SPL
[Touch HD Windows Mobile ROM Development] clotet_htc:
Hi, how do I do this?

Thanks! :-)
[Touch HD Windows Mobile ROM Development] fuithecat:
Does flashing a stock rom achieve similar result?

Or is Task 29 doing something new?

Also, will it remove the radio as well? If so, does that mean that if I flash a rom that doesn't have a radio in, I'll need to flash a radio again?

Sorry for my basic questions :p
[Touch HD Windows Mobile ROM Development] jigners:
just the usual step to enter bootloader "press and hold volume down and briefly press power button and then your device will go in tri color screen.

please read up on the first post, Task 29 needs an .nbh file to run and do its job

it is highly recommended to use a Radio .nbh file, this Radio will then be

flashed
[Touch HD Windows Mobile ROM Development] Pandemoniumone:
I would have to say the obvious answer is yes. After reading and understanding what task29 does for the device and seeing how well the Rom performs afterward (no freezes/lockups), this has become something I do before every flash.
[Touch HD Windows Mobile ROM Development] Maarten_0031:
Great! That's what I thought, but it's nice to have it confirmed. Thanks!
[Touch HD Windows Mobile ROM Development] tin2404:
What HARD SPL do you have? It seems that you have bad RUU downloaded or your device is locked :(

Please refear HERE ON WIKI PAGE for further reading and instructions.

Try to flash original shipped ROM.
[Touch HD Windows Mobile ROM Development] tin2404:
It has been reported in message from user bugsbunny that if you stuck after performing task29 on INVALIDE ID error that procedure from HERE WORKS as solution :D
[Touch HD Windows Mobile ROM Development] Jayedamina:
my device is unlocked with HARDSPL 1.56. i was just trying to clean and flash a new ROM, but i have no idea what went wrong. i tried 3 stock Roms and 8 custom Roms from different chefs and still nothing, also tried on xp and vista ...Nada:mad::mad:. later after work i will try flashing from SD...hope that works. thanks guys.:)
[Touch HD Windows Mobile ROM Development] hughey:
I had a hard time finding the 1.17 radio NBH. So when I finally did (just by extracting the .exe) I dicided to RAR it for you !

Fast downloadlink:

http://www.t-spirit.nl/files/RUU_signedRadio117.rar

Thanks for this ! Phone's quite a bit faster now...

It did scare me for a while... Phone wasn't powering up after pulling battery out @ Smart Mobility screen... But it did after a while thankfully! :P
[Touch HD Windows Mobile ROM Development] blister969:
Followed your instructions...everything is OK:) Thank you!
[Touch HD Windows Mobile ROM Development] MJRL:
Ok, everything went ok Windows 7 X64, this how i've donne it.

Download file from the first post, and put the radio file (.nbh) you want in the folder you have downloaded, in my case radio 1.14.25.24

Set HD into bootloader

Start pc with F8 pressed

Disable driver signature (I do this cause i have problems with older usb drivers that need to flash)

Connect HD to your pc with usb cable

Run uspl or if you have HSPL do nothing

After in uspl mode, and usb conected run task 29

After that your hd will be stuck in the first screen

Take battery out

Turn on HD in boot loader

Run USPL again (don't know if task 29 will remove hspl, if don't just install the rom)

Install your favorite rom

Thanks for all
[Touch HD Windows Mobile ROM Development] r_9:
I tried doing the task29 without putting my handset to bootloader, and it worked too!! Simply plugged the phone to laptop, ran task 29, and the phone went to bootloader automatically and the task29 ran normally.:)
[Touch HD Windows Mobile ROM Development] jigners:
it is the other way around, - get stuck n Mobility Screen - then pull battery out. . . . then bootloader:) then flash custom rom

to run Task 29 your device should be "on" and connected to mobile device center. bootloader comes in after Task 29 has done its job. . .:)
[Touch HD Windows Mobile ROM Development] tin2404:
For experiment purposes on CLEAN ROM....

now tested on ROM STONHANGE from here...Before procedure noticed some minor cluttering.GPS signal too long to attach to on iGo8.Waited about 30 seconds on cloud day...After task29 bugs has been gone.With HD Radio 1.13.25.24 GPS located sattelites inside 10 seconds ! Excellent work !:D

Confirmed and worked like a charm on that ROM and I recommended this procedure for that ROM also :D:D
[Touch HD Windows Mobile ROM Development] jigners:
hello mate! thanks for helping keep this useful thread:)

a thread has been started with the same Task 29

but it claims something impossible.:o:o

the member claimed 5 days of battery life after running task 29

very difficult to comprehend indeed. . .:confused::o:o

i mean I've had the Blackstone for over a year and flashed hundreds of roms on it

but 5days of battery life:confused:confused::o:confused:
[Touch HD Windows Mobile ROM Development] Roadrunner100:
The magic is in his Splash file, Jingers. It's a pukka Battery enrichment process init? I say patent the Fcuker before it gets a beard.;)
[Touch HD Windows Mobile ROM Development] Tindo1:
Im still getting error 244: Cannot be used for your mobile etc etc. Any way around this? Up(down) graded to a radio 1.09 or something similar coz i thot that was the cause of the prob. Ive had hspl 1.56 Olinex all along and had radio 1.17 or something similar. Am i doing something wrong? is there a version for the upgrade process which includes a complete ROM/radio combi update to obviate the possibility of radio issues during the update process? or should i look for a new HD specific RUU???
[Touch HD Windows Mobile ROM Development] Tindo1:
It's saying invalid model ID. I've just flashed 1.17 radio so I don't think it's a radio issue. Am I missing something or fumbling something?
[Touch HD Windows Mobile ROM Development] jigners:
the best way forward for your situation is run Task 29 with an .nbh file from a stock ROM

if you have an official ROM, extract this and take the .nbh file and put it in the same folder

as the Task 29. I know it will be a lot longer, but this could in theory pass the model ID check. (as its an official stock .nbh file)
[Touch HD Windows Mobile ROM Development] tin2404:
I also can confirmed 5 days battery life with Dusk 4.0 ROM without problem but I did not pay attention to it.It is normal behavour to me. :cool:

Also, I bought last week brand new device (Diamond ) for testing purposes, and prepared some stuff for MDA Compact IV (Diamond) so I should do some hex editing ( if it is necessery ) and test task29 on that kind of devices these days, so I am wondering would it be some progress with this task29 proccess on that type of devices.
[Touch HD Windows Mobile ROM Development] tin2404:
did you try THIS ?

IT HAS BEEN CONFIRMED THAT IT WORKS.:cool:

USE different radio.
[Touch HD Windows Mobile ROM Development] Elim:
I can confirm this(!) but the step "remove the battery" is still necessary. Without this step the ROM freeze in the boot sequence.
[Touch HD Windows Mobile ROM Development] tin2404:
but I wrotte to remove battery ! I did not say to leave battery inside device..:confused:
[Touch HD Windows Mobile ROM Development] Tindo1:
Cheers. Moved the nbh file into the same folder. It worked. Haven't assessed the battery use as yet. However, was kinda worried that moving the nbh file into the folder with the task 29 exe file would "confuse" things somewhat because when I extracted the file 29 zip, there seemed to be an nbh file - presumably or definitely Leo nbh??? Does tat have any effect on completing the process if there are unrelated nbh files in there?
[Touch HD Windows Mobile ROM Development] Sugocy:
Complete read through, needing two answer though:

What is a SplashScreen.nbh? I understand you use a small ROM/Radio ROM to make the Task29 go faster. Afterwards it'll delete everything it has installed the small ROM/Radio to i.e. the partition.

Im using a Touch HD, so I need a radio or maybe the splashscreen.nbh you all are talking about. The last thing, sounds the smallest and therefore the quickest to me;)

Of course the disclaimer about making it brick: Is is that "fragile". I thought after HSPL Oli-nex the "bricking"-spookyness was over for the most part.

Thanks in advance,
[Touch HD Windows Mobile ROM Development] jigners:
your ok, when doloop from the HD2 thread hex edited task 29, he included

the package with a small .nbh file related to HD2, we just delete this and

replace it with any .nbh file for the Blackstone, as Task 29 needs an .nbh file

so it can do its job of formatting the ROM partition (in your situation i suggested

an official .nbh ROM file as you keep getting an error "invalid device ID")

Glad to know it worked on you! and thanks for giving us your feedback.
[Touch HD Windows Mobile ROM Development] jigners:
splash screen is another term for the start up boot sequence you see

when powering up the device.

the idea is the smaller the .nbh file the faster Task 29 gets loaded.

Some custom ROMs has its own Radio, if you decide to flash

one without a Radio included, it is advisable to run Task 29 with a Radio best suited

for that particular ROM or one that is in your experience gives you the best

performance/reception etc., it will be installed when you run Task 29.

Task 29 only touches/works on the ROM, nothing else.
[Touch HD Windows Mobile ROM Development] ClydeB1:
Or as I suggested, when Task29 finishes just hold in the Volume down button ;) and it will reboot straight into bootloader ready for the rom flash so then "remove the battery" is not needed - much easier in my mind :p

After rom flash hold in both volume up and down and it will initiate the hard reset sequence and you never need to remove the battery again.
[Touch HD Windows Mobile ROM Development] WingZer0n:
Sorry a bit confused on item 3.....how to make "task29" process? run in from the phone??? Copy it to the SD card or phone main memory and run it?
[Touch HD Windows Mobile ROM Development] Danny04:
confused on item 3 of tin2404 process

FLASHING FROM SD CARD

3. Remove SD Card and make "task29" procces

Additional:

3.1 Remove the SD Card from your phone with the chosen blacimg.nbh (for example Energy or Dusk rom. Otherwise you will flashing the chosing rom! Without using the "task29").

3.2 Run on your PC the "task29" with a Radio which is best suited for your phone.

3.3 Your phone will reboot and now you are stuck in smart mobility screen, but not to worry ! That is because you dont have any ROM inside anymore ! Device is fully clean !

3.4 Disconnect device from computer, take the baterry out and insert your SD card in the phone.

3.5 put device again into bootloader mode (push Volume Down and Power button).

3.6 Once in bootloader mode, it will automatically pick your chosen rom in the root of the SD card and flashing the new rom on your phone.

Hope this help you.
[Touch HD Windows Mobile ROM Development] jigners:
no, dont put the task 29 .exe file on your device or sd card, keep it in a folder

in your pc.

there are two processes that needs to be accomplish.

1. is running task 29 from your pc with the device connected via windows mobile

device centre.

2.is the process of flashing your chosen ROM. via sd card or via usb connection

with either USPL or.HSPL.