Hello,
After 3 posts without answer in this thread http://forum.xda-developers.com/showthread.php?t=550540
I hope someone can help, see below
repost
Hello,
I read the tutorial here:http://forum.xda-developers.com/showthread.php?t=550540 for SD card only (I'm not a windows OS user)
and try to change my rom for the official HTC win 6.5 FRA but in bootloader mode I only get a white screen with a message in blue "Loading..." and nothing else after 40 min!!
Note: My TP2 is NOT branded
Did I miss something?
I went to the HARDSPL using a friend's laptop with activesync. The tutorial says activesync must be connected to the phone when launching HARDSPL. Once I launch HARDSPL, the connection by activesync is lost and I got ERROR 260
I have tried with activesync on XP and the new application on win &..All same error
I don't think this post is going to last long, since the thread where you originally posted was the correct place for it.
You said you had no answer, but that's not true, you had at least one answer from mskip, and I also made a suggestion to which you made no response other than asking if you should give up.
hi,
I did answer: http://forum.xda-developers.com/showthread.php?t=550540&page=45
Even tried: "- anyone having problems with the device entering SSPL without functional USB port ("ERROR 260 CONNECTION" RUU error), you can get SSPL-Manual-Rhodium.exe from attachment in this post, copy it to the *device* itself and run it. then once the screen is showing black, run the Hard-SPL package on the PC and select Manual"
And same error code 260
It is a GSM phone, right ? Not a Worldphone (CDMA/GSM, which has a SIM card slot but needs a CDMA HardSPL and ROM) ?
Hi,
Yes It's a GSM (with simcard)..I guess.. How to find it out?
Carrying on this discussion in the ROM-flashing sticky, no need to duplicate it here.
Related
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.....
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
Hi all,
Im trying to flash my SPL by following the sticky guide in order to install the Windows Mobile 6.5 and Manilla 2.5 ROM by Miri. I connected the device to my laptop, got an ActiveSync connection, started in Bootloader, waited for the USB sign and ran the application but the loading bar gets stuck on 0% before giving an Error. I then went to troubleshooting and tried the manual SPL flash but when it restarts in the new bootloader, I don't get the USB text at the bottom. If I try running the program, I get Error 260: Connection. Sorry if this has already been covered in a previous post, I did try searching the forum but didn't really know where to look.
Russell
I had same problem.
Change usb cable, change usb port you are using and make sure antiviruse turned off.
rgtuit said:
Hi all,
Im trying to flash my SPL by following the sticky guide in order to install the Windows Mobile 6.5 and Manilla 2.5 ROM by Miri. I connected the device to my laptop, got an ActiveSync connection, started in Bootloader, waited for the USB sign and ran the application but the loading bar gets stuck on 0% before giving an Error. I then went to troubleshooting and tried the manual SPL flash but when it restarts in the new bootloader, I don't get the USB text at the bottom. If I try running the program, I get Error 260: Connection. Sorry if this has already been covered in a previous post, I did try searching the forum but didn't really know where to look.
Russell
Click to expand...
Click to collapse
You're using sticky guide yet you created a new thread instead of posting in sticky....why? no need for this
Thread closed
p.s. for your info
ERROR [260] : CONNECTION
This error occurs when the RUU cannot make a connection to the device right before flashing. This typically happens when you try to flash a new SPL to your device. Use Soft-SPL before attempting the RUU again.
If this doesn't work, try resetting your device, put it in bootloader and then connect it to usb cable
I need to upgrade my i-mate but the RUU gives me the Error 120: Country Code Error...
Anybody can solve this?
-Thanks!
put your device in bootloader mode before connecting, and use maupgradeut_noid. that question has been asked and answered hundreds of times, please search the forum next time you come along a problem
In order not to multiply the topics:
I have succesfully upgraded my Tmobile MDAIII to Win 6.1 via the mentioned above method. And now I want the start-button-in-the-bottom
So I downloaded the image file, put MDA into a bootloader, plugged it into craddle, started maupgradeut_noid and... the second screen didn't show any data about the device. (in FAQ "something went wrong, start over again" is advised). Several attempts were of no use. The fresh XP SP3 also didn't help. What is wrong??
By the way, the official upgrading software (that one that shows Invalid country ID later) does show the device info screen correctly.