Database Develop

Updating to WM6 ROMs on Vista

Hey All-
I'd appreciate any help anyone can offer. I am having problems updating to any of the WM6 ROMs out there (up here). One of a few things is happening:
1) Either RUU crashes just after it successfully sends my PDA in to bootloader mode, or
2) RUU is able to stay up, but for some reason, does not like the update file:
I either get an error: "This NBF file cannot be used for your PDA Phone. Please get a newer NBF file.", or
it suggests the nbf file is "corrupted", I think indicating the RUU util I am running is out of synch with what the PDA is expecting.
I'm using a T-Mobile MDA (Vario?) and Vista.
I've tried all of the solutions I have been able to find:
* changing the driver to HTC USB Sync so that it can "reconnect" once in bootloader
* various flavors of the update utility to get around the crash, which do not let me upgrade to the ROM of choice!
* hard reset of the device
* I even tried pulling down one of the ROM upgrades from the T-Mobile dowloads site and dropping that in with a WM6 ROM nbf file. That was a huge flop.
I know people have done this! I've seen it over and over again. So what in the world stupid thing am I doing to not make this work?
Thanks.
Joel Niemeyer
Seattle

RUU doesnt work on Vista. Use shelltool.

Thanks for the advice. I'm sure it was good advice, but I am three hours in to it running now, and I don't have a good feeling about it. I think it says it would take at least 15 minutes. Not 180! Ugh, now I wonder what I should do?
Joel

jniemeyer said:
Hey All-
* changing the driver to HTC USB Sync so that it can "reconnect" once in bootloader
Click to expand...
Click to collapse
How do you do that? Thank you because when i try to downgrade my ROM or w/e so that i can unlock it when i gots to bootloader the fred green blue thingy it doesnt reconnect to active sync and maybe thats my probelm...=[

chaos, just look around for the RUU with Vista instructions- they are everywhere!

hey mate,
just follow this instructions http://www.modaco.com/index.php?showtopic=252977 to falsh every official ROM under MS Vista. Surely, when it comes to WM6 you gotta use the Shelltool.
regards
irm

Answer for Vista
My question is why don't people just dual boot vista with xp or 2000/etc...that would solve a lot of issues about the problems with vista.. just boot to xp..
I figure if you have the $Funds$ to spend on a $250+ phone you could shell out $50 for a 150gb 16mb cache HDD for your pc and dual/tri/quad/etc... sheeet son i've been doing this for years with linux/m$/mac.
Gotta face it, some software just runs better on one OS over another. peace out.

can someone confirm shell tool work

ANTC said:
can someone confirm shell tool work
Click to expand...
Click to collapse
I tried it, took like 6 minutes then it was completed, knowingly it wasnt flashed right, but did the hard reset on the phone and was stuck at the SPL screen, so just loaded up VMWare to reflash.

It worked for me...
I flashed one of the WM6 ROMs using my Vista Ultimate computer. One of the main parts in making the thing work is remembering to put your computer in bootloader before doing it. On post #7 in the MoDaCo thread, it says this.
Once more, here is the link: http://www.modaco.com/RUU-on-Vista-It-can-be-done-the-ultimate-guide-t252977.html

so your saying witht hat tut you flash a custom rom??

Yes
Yes I was able to. I don't remember which, but I think i was Core 2.0

Yeah, I was able to use shelltool to make this happen. Thanks for the feedback, folks. Only hang up was that it had appeared to have seized up (was seemingly stuck before the "End" portion). I waited for like 3 hours before I finally threw up my hands and hard reset the unit. Low and behold my wizard booted up in to the new ROM and I have been good to do since!

My turn to brick it...

Hi All
Owning a Vario III and using Hardspl I upgraded to the latest incarnation of HTC's ROM (WM6.1). Having been caughtout with the freezing issue and after reading some posts about removing Hardspl I began to do so.
After reading the Idiots guide which stated :
'2. Flash the OEM ROM to your device (this will restore your OS but not the bootloader, we'll get to that below)'
I couldnt locate a proper T-mobile Wm6.0 ROM so thought as I'm just getting rid of the Hardspl I'd use the standard HTC ROM WM6.0 which went on fine.
This allowed to rid my phone of the HARDSPL.
I was then getting the Vender ID error when trying to load the new WM6.1 HTC ROM (which of course I would get as HARDSPL had been removed).
I then thought sod it and Ran SSPL-KAIS.exe and then began to run the latest HTC ROM. It started fine but bombed out at 15% and then I was left with a Tri-color screen and the message below :
In the Upper right hand corner it says RUUNBH
On the left side a little lower it says
KAIS1*0
SPL-1.56.0000
CPLD-8
At the bottom of the screen if I have USB plugged in it says USB, if nothing is plugged in it says Serial.
I cant seem to run MTTY 1.16 or 1.42 as I'm using Vista and the processes are slightly different (though I stopped what I thought were the relating ones to no affect)
Anyone on this awesome forum got any bright ideas as to how I can resurrect this one ?
btw : if I/we do manage to fix this one, do you think it will be possible to a) have a copy of the OEM T-mobile ROM ?? b) still upgrade to latest Wm6.1 ROM without the need for Hardspl ??
Cheers all
Steve

RUUNBH errors are from incomplete flag clearing after a flash. All that is needed is MTTY, 1.42 is best, & a few commands.
The first command is:
cmd>set 16 0
The second based on what SPL you now have (1.56) is:
cmd>boot
For use with Vista, you'll need to follow the dirsections used to flash via vista, & roll back the USB drivers. Do a search for Flashing with mtty and vista in google.

FANTASTIC !!!
Many many thanks for your prompt help !. Magic.
Im back up and running thanks to you brilliant help .
Do you think its worth trying again to Flash the phone using SSPL-KAIS and the latest HTC ROM ? or do u think I should quit whilst I'm back up and running ?
Alternatively, is there a way for me to sidestep the T-mobile lock without using HardSPL ?
Apologies for the questions, but after reading the many many posts on this, my brain is deffo boggled !!
Big thanks
Steve

can not flash button rom

HI.. Im a newbie here, just got my g3 wizard ipl2.25 / spl2.25 couple weeks ago and seen what you can do with them. phone is sim and cid unlocked. i would like to flash to wm6 eventually all thought im running into problems. i followed all the guides to upgrade. tried on my vista 32 bit and win xp sp2. every time i run the button rom to downgrade, i get "romupdateutility mfc application not responding" on vista and "error 260 or 274" with the xp. ive tried it in bootloader mode, restarting pc and wizard, tried different driver for vista, and shut down AS and WMCD before attempting to flash. ive been at this thing for weeks. firewall and antivirus turned off on both pcs, phone is at 100% charge. once in bootloader i get usb at bottom of screen. so i know i have connectivity. run rom not in bootloader, identifies version, then goes to bootloader, then i get error. run again and it dont even identify wizard. happens with both pcs. any ideas please help. i have already read, read, read and still cant figure this out. any ideas are greatly appreciated.

First of all,as you say its SIM/CID unlocked already then why are you trying to downgrade with Button's Rom,its only needed to downgrade if its required to CID unlock.If you are sure its already CID unlocked than simply download any wm6 rom and flash to upgrade,but if you are not sure if its CID unlocked,download WST_4.2.2 tool and run it to verify the CID lock/unlock status.

sorry i made a typo. it is Locked both sim and cid. typed last night at 3:30 in the morning. i ran the wizard service tool and thats what it told me. sorry again

check firewall (even XP one) / anti-virus settings, avoid using front panel USB, avoid usb cables with electric components, try different RUUs, avoid Vista, try another XP computer

Take all the precautions mestrini has posted above and always try on a winXP machine,don't use vista for flashing.May be the Button's rom you downloaded is not a correct package,try to download it again or from a different download link,you can even downgrade with official AKU 1.xx rom if you can find and download.

thanks for all the idea. definately stop trying with vista. i already have tried downloading button rom from a different link, no electronics in usb cable, and firewall and anit-virus have been disabled. i just found a aku 1.xx rom last night so im going to try that tonight. thanks again

well i tried all that and still nothing always get a error 274 connection code. my xp is ran through virtualbox on a ubuntu machine. could that have anything to do with it? i can run WST that works fine. one thing i have noticed though is when my wizard goes into bootloader my connection gets lost and usb connection icon comes up with unknown device and a different pid # then if phone is just turned on, and no check next to it. i tried activating it while ruu is searching and that immediately gives me a 274 error. is it normal for product id to change when in bootloader? by the way i was using the cingular 1.08 ship rom this time, tried it about 15 5itmes with same result everythime. never touched the phone and never took out of bootloader.

litlldevill666 said:
... my xp is ran through virtualbox on a ubuntu machine. could that have anything to do with it? i can run WST that works fine. one thing i have noticed though is when my wizard goes into bootloader my connection gets lost and usb connection icon comes up with unknown device and a different pid # then if phone is just turned on, and no check next to it. i
Click to expand...
Click to collapse
I think you touched the wound!!
I guess RUU can't communicate properly through virtual box. Please try another XP machine before anything else (i think you can manage a friend with one since M$ is so spread - unfortunantely )
cheers

well thats what it was, i did a dual boot on my linux laptop with xp sp2. ran button rom and flashed first time. thank you both very much.

litlldevill666 said:
well that's what it was, i did a dual boot on my linux laptop with xp sp2. ran button rom and flashed first time. thank you both very much.
Click to expand...
Click to collapse
Thanx ! it was pleasure to help you,hope you upgrade it successfully,do let us know if there's any problem,we are always here to help,Thats what this excellent forum is all about !!!

please help downgrade wizard g3 wm6.1 tnt romto wm5

i have searched for a long time and cant find any answers i have a tmobile mda ive tried running the tmobile rom and it didnt work gave me an error any advice please help me i wan wm5 again

Download Official T_mobile wm5 Rom from this link,bet the phone in Bootloaders (RGB screen) and flash to recover back to its default status,then read carefully this guide fron the below mentioned link and do the unlocking and upgrading.
T_Mobile Rom:-
http://rapidshare.com/files/38880130/ruu_prodigy_226102_22610105_022511_tmous_wwe_ship.exe.html
Unlocking Guide :-
http://wiki.xda-developers.com/index.php?pagename=Wizard Windows Mobile 6 for newbies

thats the prob when i do iit it takes me to the rgb screen and the comp says error any info for that

Exactly what error it displays,it must with an error No. and some explanation about it,can you recall it correctly.Does it display Communication error ?

pmed error 260 communication

Ok,I hope you are doing all this on a WinXP machine,if its a vista,it won't work,WinXP is recommended.Now,before start to flash,close/disable any Anti virus and firewall running on the pc,and also try to close as many applications running on the desktop or background through Task manager,don't surf the net during flash or do any Office work.
Close/disable Activesync,coz its not needed while flashing,end the process 'WCESCOMM.EXE' in the Task Manager,delete any Partnership with Activesync.
To check the connectivity problem,get the phone into Bootloaders (RGB) and hook up the phone with pc via usb cable and watch small usb appear at the bottom of the Bootloader screen,if its there,its establishing connectivity,than its good to go and run the flash,but if its not there,then its a connection problem.It may be the usb cable or mini usb port of the phone is faulty,check this out and do the needful.
Many communications errors are also due to dead or discharged battery,it doesn't have enough juice to complete the flash,hence,results in comm error,always start to flash with a fully charged battery.

le problem was the laptop i used a different one and its almost done i got another ? if i changed the radio am i gonna have to get the original tmobile radio too or does it change with the downgrade

Original ROMS
lorijuan1024 said:
le problem was the laptop i used a different one and its almost done i got another ? if i changed the radio am i gonna have to get the original tmobile radio too or does it change with the downgrade
Click to expand...
Click to collapse
The Original ROMS got his Radio ROM included. in fact... Stck ROMS got...
IPL and SPL
Extended ROM
Operative System
Radio Version

Can this be done if I have Vista?
I know someone mentioned installing a rom won't work with Vista, but I was hoping maybe it was just a personal preference. I have two pcs that both run Vista and Linux. My problem is, the wm6 rom (faria crossbow) doesn't work by default and I have a cracked screen so when I try to set it up I can do every step except setting the proxy port #s because when I highlight one there's no way to tap on it, and pressing or holding the select button (the button in the middle of the 4 way joypad) doesn't allow you to edit the values or pop up a context menu. I was hoping to get my $5.99 internet or at least my email and mms working but I got layed off and the holidays are coming so I prob won't have the extra (I know its not much, but I have no job) $30 to buy a new screen until sometime in the new year.

Why not downgrade to the Button ROM, and then upgrade to WM5 afterward?
Chuck

[Q] ROM Flashing from PC on Mac - not working

I am trying to flash the ROM on my Touch Pro 2 before I sell it. I am running windows XP on a mac using Parallels 5.0. I have tried running the ROM update when active sync is connected and all starts ok then I get error 226 saying cannot connect. I then tried flashing straight from a newly FAT32 formatted microSD card and that jsut stocks on with a Loading message. So I tried flashing Hardspl, although I think that I have done this before when I still had a pc, but that failed with a connection error too. Any tips/advice anyone?

You need to provide more information. Are you trying to flash a custom ROM, and which one? What ROM are you running now? What version of the phone do you have/what carrier?
If you are still HardSPLed, the second line of text on the bootloader (tri-color) screen will say "OliNex", probably saying "SPL-0.85.Olinex". If it doesn't say this, the SPL is locked, and you won't be able to flash a custom ROM.
If you are trying to flash the stock ROM, I think some people have been having trouble doing so with the phone HardSPLed. But it may depend on what stock ROM. I am able to flash the Euro stock ROM just fine on my HardSPLed phone.

ok, i'll try to answer your request for more info:
trying to flash Energy Rom build 23699.
Existing ROM version is listed as 2.07.401.1 (80303) WME dated 2/4/10.
Phone is an unbadged HTC Touch Pro 2 as sold by Tmobile etc in UK.
Can't see any mention of OliNex on bootloader screen, so perhaps I didn't unlock= it after all. Certainly no T mobile stuff left on the phone now.
??

jbevan said:
ok, i'll try to answer your request for more info:
trying to flash Energy Rom build 23699.
Existing ROM version is listed as 2.07.401.1 (80303) WME dated 2/4/10.
Phone is an unbadged HTC Touch Pro 2 as sold by Tmobile etc in UK.
Can't see any mention of OliNex on bootloader screen, so perhaps I didn't unlock= it after all. Certainly no T mobile stuff left on the phone now.
??
Click to expand...
Click to collapse
Don't know off hand what ROM that you have installed right now. What do the boot screens look like when you start the phone? Also, what does the bottom row of red letters say, when you startup the phone?
If it doesn't say Olinex on the bootloader screen, you are not HardSPLed. Either you never did it, or you relocked it.
Run HardSPL, and you should be able to flash from the SD card no problem.

Redpoint. Thanks for your replies and interest. I have tried to run HardSpl but this fails with a 260 connection error, even though Activsync is synced and connected. Id this to do with running a virtual pc on a mac perhaps?

Your welcome, hope my advice is helpful.
HardSPL is pretty finicky, even on Windows Vista and Windows 7 systems. I think running it on a Mac is difficult or even impossible. You can search the HardSPL thread and see if anyone was able to get it to run on Mac. I'm pretty sure I read different users on that thread mentioning issues with running HardSPL on Mac.
My best advice would be to run HardSPL on a friend's Windows XP system, if possible. It usually runs smoothly on XP, and only takes a couple minutes.

Yes, that confirms my suspicions. I will try it frommy partners windows XP netbook whenshe gets home. Fingers crossed.
Will let you know how I get on and if I need any more help!