Related
My wife has a pda2k that the phone quit working on, the pda functions are fine. I was able to upgrade the rom and ext rom but when I try to upgrade the radio it always fails. I have been all over this site and the web nothing has worked to flash the radio. When the flash progarm runs I can see the rom and ext rom versions but nothing is displayed for the radio. I have tried all versions of the roms I have found. Always the same the radio fails, I had to remove the radio rom from the dir. to get the others to update, I then tried the radio alone several times, several different waysand it always fails with various errors.
Thanks for any help.
Husband with a ticked wife please help!
hey,
put ruu.dll, radio_.nbf and MaUpgradeUt_noID in a folder, and run the maupgradeut.exe file...this should upgrade the radio rom only, that is the gsm part.
let me knw whether it workd...
Did you follow the wiki radio upgrade only instructions ? if so what is the error?
I have tried both options listed above, the upgrade starts sits at 0% for several minutes then fails. I do not remember the exact error, this is what happens every time.
put ruu.dll, ruu.conf, radio_.nbf and MaUpgradeUt_noID in a folder, then put your device into bootloader mode by pressing power, reset, and record buttons at the same time, this combination of buttons will show "Serial" and bootloader version on your screen, then place it on the cradle, the "Serial" should change to "USB" then kill activesync (open task manager and kill rapimgr.exe and wcescomm.exe) then start MaUpgradeUt_noID.exe and all should be fine
if an error pops up please let us know
xplode said:
put ruu.dll, ruu.conf, radio_.nbf and MaUpgradeUt_noID in a folder, then put your device into bootloader mode by pressing power, reset, and record buttons at the same time, this combination of buttons will show "Serial" and bootloader version on your screen, then place it on the cradle, the "Serial" should change to "USB" then kill activesync (open task manager and kill rapimgr.exe and wcescomm.exe) then start MaUpgradeUt_noID.exe and all should be fine
if an error pops up please let us know
Click to expand...
Click to collapse
This not working. I Has the same problem. It seems like HW problem. Can't update radio. Then BT address 00:00:00... And now it freez at startup always.
IMHO. This is bad Flash which died.
I am waiting for answer about a month an still haven't one.
SoftService is right, if this type of upgrade fails it may be a hardware issue
I created a directory with the files listed and this is the error message I recieved:
error 114: radio rom update error
Any Ideas?
Thanks
do you have a sx66?
Anybody here has Full flash from PH20B device?
I think fullflash will help us from that problem. But it will the question how to unlock device after this procedure.
And anybody know how to repair IMEI?
Is there hardware specialists?
MDAIIIUser,
Mine is labeled PDA2K. It has quit syncing now. It just seems to be dying a slow agonizing death, and it's taking me with it! I need my electronic brain back.
I have tried all the suggested steps repeatedly. I am getting nowhere. It seems to want to work, it just keeps erroring out.
Thanks.
I had yesterday some problems regarding radio upgrades, which can not be solved by WIKI, so :
my radio rom was TYPEII and the files for upgrade are TYPEI => It can not upgrade
Tryed radio 1.13 TYPEI with TYPEI files and NOID => error
then tryed radio 1.13.1 TYPEII with its TYPEII files and just copied into that dyrectory the NOID APP and it worked (i have just learned that MAUpgradeUT_NOID.exe works with TYPEII RUU.dll and RUU.conf)
I was surprised because i use NOID for upgrading my roms and the files are TYPEI
Hello,
I have this rom : RUU_Trinity_LVSW_WWE_1.25.0.8_GPS (AKU 3.5.2)
from http://forum.xda-developers.com/showthread.php?t=302198
I wanted to test the new WM6 roms, unfortunately, my trin doesn't update with any rom I tried (Orange, HTC, LVSW Wm6, Mun_Rus Wm6, ...)
It tells me : "ERROR 262 : UPDATE ERROR
... communication error during the process"
I'm stuck on LVSW Wm5 rom :'(
Not sure if Des SPPL is causing this problem... anyway, I tried to update it from Bootloader or synched, on XP and Vista, 5 differents roms... no luck.
I would really appreciate some help, thanks
can you list the steps of what happened, in order?
also, just to make sure i understand, have you already tried to manually enter the bootloader and THEN run the RUU? *edit* one last question, have you tried this.. after the error, leave your device connected and in bootloader, then restart the RUU.. can you give me your device details too?
Well, when I run the update with normal step (connect AS, then launch update...) when the update is ready to be started (progress bar appears), phone have to switch to bootloader, which it does. However, it seems that the RUU is waiting for that since it return me this error:
ERROR 246 : Device not responding
And I have to exit. I don't understand ?
Progress bar didn't even appear on the phone.
At this time boot loader shows
IPL-SSPL by Des
SPL-1.07.ds
So since I'm already in Bootloader mode, i try to launch RUU again. Here is the error I get when the progress bar appears on both phone and PC :
ERROR 262 : Update Error
And it offer me to recover the device, which I don't need as the current rom has been left untouched and is still functionning after the error.
Then I reset the device to enter bootloader this time:
IPL-0.50
SPL-1.06.0000
same error : ERROR 262 : Update Error
I'm kinda out of option, thanks a lot for your help !
well, it's been a pretty common thing for the RUU to give an error when the device goes in to bootloader (can't detect it for some reason). Most times, simply running the RUU again while the device is still in bootloader works fine.
Why don't you put hard-spl on just in case, manually enter bootloader (which will then be hard-spl) and run the RUU again. You shouldn't enter the bootloader manually unless you've loaded hard-spl or sspl on to your device. From what i understand you won't be successful from what you did after the hard reset. When your phone went in to bootloader the first time, it was with SSPL pushed to your device by the updater program to enable you to update safely. After resetting, you're back to your normal bootloader which won't help anything.
I know one time it did this to me, and wouldn't connect to my device. I started the RUU about 3 times in a row with my device on bootloader, and for some reason after the 3rd time it suddenly worked.. weird, i know.
anyway, hard-spl will make the whole process safer.. let me know if it connects or not, i'll see if i can help you troubleshoot
I wanted to install hard-spl, but it runs as a normal RUU and give me exactly the same errors as a normal run update (error stated above).
So I don't see how I could install it
Another thing weird, when I run a official HTC rom update, when the udpdate should start (device enter in boot loader, progress bar appear in bot PC an device), the Trin reset itself and boot as normal... of course the RUU gives an error due to this reboot ...
Same weird behavior with an official Orange rom...
Now I'll try with SSPL...
Oh and thanks a lot for your help
simply try to run twice ROMUpdateUtility.exe after error
Please read carefully what I have posted (and the steps I ran into)...
Already launched again RUU, it gives me an Update Error and the device is stuck on the screen that show the progress bar.
Need to soft reset... I can't launch again the RUU after that since the device is no longer recognised as connected on PC.
I confirm I can't manage to install the Hard SPL, even after laoding Des sspl from the device...
Defintly blocked
At last I have succeeded in upgrading the device. Seems like my bootloader was somehow corrupted or something... after doing another Hard Reset it have installed hard spl succesfully...
I had already done a hard reset before, so I don't understand what happened.
Nevermind, at last i can try wm6
thanks a lot for your help racerx_ anyway
hey no problem.. not sure that i actually helped haha.. but i'm glad you sorted it out. happy flashing!
Might it have been the USB driver on the desktopside ?
Did you see XP recognize and install HTC USB device again, after device disconnecting from AS and going into bootloadermode for first time ?...
Just a thought...
Not sure what it is, but it's happening again, can't update anything as the bootloader seems somehow corrupted.
When i enter bootloader it briefly display the 3 color, then grey screen with "loading" and then the hard spl screen from Olimpo... the only problem I see is that it does no longer display TRIN100, but only little dots (like if it was corrupted)...
Very annoying situation, and I have already done some hard reset, but nothing
So more exactly, where I start DES SSPL or when I enter Olipro Hard SPL (that I installed before WM6), it shows the good infos like :
TRIN100
xxxx
TRIN100
SPL-
But after 1/4 of second, it start loading for a very short moment
and display again the RGB screen with the infos except the "TRIN100" parts are like this ':':':':':':
Anyone has seen this before ???
@cedrick: You have a SD card inserted on this device, right? if so, remove the SD card and try again.
If the SD card is not the problem, then you might have overwriten the memory region where the ModelID is stored. I can help you to recover it if that is the case.
pof said:
@cedrick: You have a SD card inserted on this device, right? if so, remove the SD card and try again.
If the SD card is not the problem, then you might have overwriten the memory region where the ModelID is stored. I can help you to recover it if that is the case.
Click to expand...
Click to collapse
...... well well, that was simple hahaha (and I feel stupid lol).
yes I had my SD inserted (and I remember only now that the last time it worked I had indeed removed the mini-SD).
So, thanks to you I have understood this issue at last !
Muchisimas gracias por tu gran ayuda pof
Now the question is, wtf do u have on this SD card? LOL
Errr that's a good question... maybe it is time to clean those 4go of things (which most of those come from the SD I had on my Prophet, in the top of that)
Anyway, it's a rare specimen indeed... want a copy to play with heh ?
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
I've spent whole day reading through the froum and the trinityguides.info site but can't find any proposed solution to work for my situation.
Device info:
ROM version: 3.00.707.17 (WM6)
ROM Date: 6/29/07
Radio version: 1.46.00.11
I've tried using all 3 versions of hard-spl but they all end up with the same result. With active sync linked and ready, ran the "romupdateutility.exe" at the end the PDA prompts if I want to run the "enterbootloader.exe", the moment I press yes the active sync connection would drop and eventually the program timed out with error "260" while PDA stuck in the tri color screen displaying the following:
TRIN100
SPL-1.07.ds
I've found some similar problems in the forum but those users are using vista however I am running XP sp3 in this case. I've tried all other solutions in the FAQ areas but none of them works.
My unit came with the WM6 already but I just want to upgrade the radio and get some cooked ROM to get faster performance. What am I missing here?
Any help is appreciated.
Once it drops to the tri-colour screen and is in bootloader, run the RUU again. Should be all that you need.
I've tried running it over and over but on the bottom it just kept on saying "serial" when it suppose to say USB.
Anyways, problem solved and it turned out to be the cable. For some reason the cable is good for anything, except keeping the phone connected/recognized while in bootloader mode.
I think this should be listed as one of the FAQ in the trinityguide. This might be a rare problem but it surely took me a lot time to figure out.
on Vista
Hi,
I have similar problem but I'm using Vista (Business). Is there any workaround ?
Regards,
Daneal
Hi
I have the same problem
spl 1.20 Olipro display serial instead of usb
I tryed several usb cables and still the same
when trying to update the rom it refuse to connect the ppc and end displayng the 260 error no connection
My system is vista and the first time I upgrade everything was fine, I followed all tutorials and no problem at all.
Do you think that could be this new 6.1 Mobile device center I recent install the cause?
best regards
Inabox
The problem isn't the WMC as such more the fact its Vista. Find an XP PC and do it from there.
Hi there, I had the same problem just now and cured it(in Vista). Just upgrade the htc driver in device manager again with "wceusbsh.inf" previous file, then should be ok. It seem to be Vista replaced the driver during it switched to Tri color menu.....
Hi,, I have used shelltool to install TNT 6.1 from wizlove all went smooth
Then i decided to try a different radio so flashed 02.71.11 from o2.37.11
all went smooth no problem,, It wasnt a day and I had to get rid of 02.71.11
so tried flashing to others and ruu loses conection on status bar and screen goes into the tri col mode,, since then I have tried to do hard spl and it gets as far as the white screen and then ruu says lost connection, so I used shelltool to flash back to wizlove but after reboot stuck on splash screen
I can get into the tri colour bootloader screen the usb shows but cant get any connection to ruu
Im G4, ipl 2.16.0001
spl 2.16.0001
gsm 02.71.11
os 2.26.10.2
help me please head is sore from reading too much
Thanks
What IPL/SPL it displays now and which windows are you doing on? If its vista it won't work.WinXP is highly recommended for HardSPL.Don't use Shelltool go for HardSPL or SoftSPL.
zabardast_1 said:
What IPL/SPL it displays now and which windows are you doing on? If its vista it won't work.WinXP is highly recommended for HardSPL.Don't use Shelltool go for HardSPL or SoftSPL.
Click to expand...
Click to collapse
ipl spl as posted,,,,,I have already used shelltool to load TNT and then I tried to run hard spl but ruu says lost conection on white screen so I used shelltool to go back to wizlove but on reboot it is stuck on splash screen, and Im on xp
Ah ! yes,its G4,ok,HardSPL won't work in Bootloaders (tricolor) it'll only work if working OS is running.
Which windows are you on vista or winxp ?
Im on xp,, but as I have posted Im now stuck on splash screen
It is almost bricked
So try to reflash an original ROM dont install wizlove (it wont be a diference but...) in RGB try to run the RUU from original EXE package id dont works is almost bricked.
Try to get a backup from another device fully functional following the steps indicated by Drug store on splash screen stucks solution DIY thread if dont works or you dont have a backup Minisd so try the MTTY...
I am CID locked G4
Download Official k-jam stock rom from the below link and flash it in Bootloaders,recover back to default status and than proceed further:-
http://www.imate.com/Support_DeviceSupport.aspx
G4 devices cannot be CID unlocked like a G3 phones,in this situation only official stock rom will get flashed,it contains IPL/SPL for both the devices,it shud flash and work.Than after recovering back ,Apply 'HardSPL' to semi-CID unlock the phone and upgrade to any wm6 rom,don't use Shelltool,it sometimes creates problem.
I don't think Backup rom through minisd with MTTY will work in this situation, but than, thats me !
OK I got the official rom, but same problem RUU says it hasnt got a connection the phone is in tricol boot load at this time, I think the issue is how to get a comunication between the RUU and the wizard in in Tricol mode surely someone has an answer on this?
OK.... it seems to be your PC...
When you plug your device via usb in the pc port the dev shows USB bottom left on screen... ? Does the PC shows you "Unknown device, please intall the drivers... or has a bad function"?
The USB cable... maybe your battery is low.... maybe the USB PORT... i dont imagine anymore problems... Try to get a full batt.. other USB cable and other PC XP of course... and retry.
OK a glimmer of hope,, I switched to another usb port windows loaded driver etc, then i ran the official rom ruu and,,,,,,,,,,,,,invalid ID cant run this utility,
does this mean I need the original software and how would I know what version that was,,,,,,,,cause I wasnt making notes
DAMN!!!!
OKJAM said:
OK a glimmer of hope,, I switched to another usb port windows loaded driver etc, then i ran the official rom ruu and,,,,,,,,,,,,,invalid ID cant run this utility,
does this mean I need the original software and how would I know what version that was,,,,,,,,cause I wasnt making notes
Click to expand...
Click to collapse
FIIIUUUUU!!! it seem that you have comm conection betwen the RUU and the device... but Wrong ID?
Download the file zabardast told you... it is from your carrier.
If this is the one u have tried...
so try another one... from Tmobile prodigy 2.26... or from qtek 9100 2.19 official Stock ROMS.
OKJAM said:
OK a glimmer of hope,, I switched to another usb port windows loaded driver etc, then i ran the official rom ruu and,,,,,,,,,,,,,invalid ID cant run this utility,
does this mean I need the original software and how would I know what version that was,,,,,,,,cause I wasnt making notes
Click to expand...
Click to collapse
hmmm,ok,download this RUU attached and extract it, replace this RUU with the RUU in the official rom and run this RUU from the Rom,hope it'll flash.
Or,download the K-jam official stock rom from here :-
ftp://ftp.clubimate.com/K-JAM_WWE_21...20710_ship.zip
I tried all that and still not getting anywhere, constantly the same problem re connection I do get the found new hardware when trying different usb ports but the ruu complains " no connection" I cant seem to get what it did before in terms of getting further to the point where it told me invalid ID I will have to try another pc with xp but dont have one handy
Might not be bricked..
check out this thread, it might be of help