Related
Firstly I would like to say thanks to this site and the trinityguides.info site for the great work people have being doing and making available to everybody, it is great being able to use my trinity with wm6, keep the good work going!
Now the issue I seem to be hitting the same "error [260] connection" every time I attempt to update anything on my Trinity. I have followed the advice on the trinityguides site regarding being stuck in bootloader mode to no avail, and I can't seem to find anything in the posts on the xda site which will rectify the issue.
Previously I have been able to update to AX3L v2.8.01 version without any problems, but I decided to update to sammy's ultra light, it initially kicks into des' crashproof sspl, but then it can't connect to the pc. even when I manually enter olipro's hard-spl it does the same. I have tried to re-install hard-spl, but can't. Disconnecting the usb option in the activesync settings doesn't do anything either. Does anybody have any suggestions for me please?
I am not even too sure if my trinity should have both Des' crashproof and hard-spl on it at the same time? Could someone advise me on whether this is alright please?
the tech details:
Trinity
AX3L_OS_v2.0.8.2
radio - 1.46.30 (even though it doesn't say this in the device info, or boot screen after soft reset)
Home PC - XP (just in case)
Did you also try flashing it again, the ROM I mean. I have this error also but as soon as I execute the ROM flash again it finds the device and starts flashing:
http://forum.xda-developers.com/showpost.php?p=1449597&postcount=2
I am assuming you mean flash with the new ROM, sammy's in my case?
yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)
No, I am in the same situation. The first attempt puts the device in 'ipl-sspl by des' bootloader mode then after about 10 seconds or so the error[260] is displayed on the pc. If I exit the ruu app and attempt again, nothing new happens on the trinity (i.e. it is still in Des bootloader) and the message is displayed again.
the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.
What operating system en activesync are you using?
On the PC I am using XP and Activesync 4.5
Check your connection settings to accept USB connections. Also, try using Hard-SPL 1.30 before flashing the ROM again.
deejacker said:
the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.
Click to expand...
Click to collapse
In your PC, try another USB connection.
BLOODY HELL!!! It is the simplest things which we often forget to try. Thanks Jotam for pointing out an obvious point, it must have needed a re-plug of the usb cable into another port for the pc to pick up the device again. I will remember that for future updates so I don't make a dumb ass of myself again. Thanks guys/gals.
Vista
Using Vista? if so which version?
Hi I asked this question yesterday, I am a noob :-[ but the only difference is I'm using Vista Ultimate.
Just for others who have the problem.
When you replug into another USB port (Luckly I've got two on my laptop..)
I used the Vista drivers from TrintyGuides and bingo !
now I try and flash a WM6.....English or Italian...maybe French.
Thanks for the help I keep you posted.
Richard
It works
Now to discover the joys of WM6 after only having WM5 for two weeks....
/i am getting the same only rom update 3.14.4.1 now sees the phone..
has the device name changed???
evene exploit no longer sees the phone
sorry, can you be a little more clear.. what ROM are you flashing, and what exactly is happening?
by the way... i thought error 246 was the connection error... am i mixed up? which is 260?
This seems to be on any rom bar the Dopod roms
and it says 260 connection error
Error 260 connection error - the phone is not going in to bootloader mode - and the RUU cannot seem to initiate communication with the phone.
I'm getting this a lot recently trying to flash.
However, Hold the power and camera buttons while resetting with the stylus (keep them buttons held down).
When you get to the bootloader - plug the phone in - wait till you see the USB at the bottom of the bootloader screen - then run the RUU again - it WILL work - every time.
I used to get this error message alot. sometimes the programs you install don't allow you to update even if you force the phone into bootloader mode so you have to hardreset the device and then upgrade.....hope this helps
htc diamond stuck
T-Rob said:
yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)
Click to expand...
Click to collapse
hi ,
my htc diamond stack, no respond on the screen i try to do hard reset with tree buttons but its not working, nothing happaned, screen stay home screen with the time and not responding touching the screen at all
please emergensy help
First of all: I read the Wiki, I followed the instructions, and I could once get it back to life.
But I want to know WHY this happens over and over again.
The story:
I have a MDA Vario II (Hermes, Tytn) for a long time to sync my business mails and calendar- entries. Some Time ago I found this Forum and updated the Device to Windows Mobile 6 (i'm Using Schaps 3.54b) and everything works like a charm.
A few weeks ago my boss as well got the same device, and unfortunately he saw me using Windows Mobile 6 while he was using the T-Mobile Windows Mobile 5.
He wanted me to update his device as well. As I did not have ANY Problems with WM6, I did not hesitate to update his device as well.
The devices are like "clones":
Same Radio- Version 1.51
Same OS - Schaps
Same Applications: Onebridge Mobile Client as the only "non-schaps" - App
Same Configuration: HTC Home without Sound- Tab, no other Extensions on Home.
Same Provider (T-Mobile)
Of course they have different IMEI and different MAC_ Adresses, but that is what it is supposed to be.
But since I gave the device to my boss, he already had the problem the second time: The device will not go over the Windows- Mobile- Splash- Screen. The first time I did not search the WIKI / Forum and just did a Hard- reset and everything was fine again.
Today problems started the second time: First of all the device was not recognized by his laptop (and my laptop eather) any more: It said "Unknown device". And while it always charges (orange led on) for the first few seconds after re- pluggin, it stopps charging after the error- Message on the laptop.
So I thought: Maybe an akku- problem and interchanged his akku with mine.
And now i have the Windows- Boot- Stuck- Thing again.
It's not that I could not reanimate the device by Hard- resetting it, but I want to understand the reason:
How can it be, that exactly the same hardware with exactly the same software reacts that different.
By the way: This already is the second device for my boss, the first one has already been exchanged... After it had Boot- Problems (I reflashed original Radio, Firmware, so that they did not say anything)
Can anyone help ?
EDIT:
I tried leaving the battery out for 20 Minutes -> no success
I tried leaving it in Boot- Screen for 10 Minutes (or even more) -> No Access
I connected it to my PC and it can be found and gets an IP- Adfress that I can ping, but ActiveSync does not connect and the Screen is still a Windows mobile Boot- Screen.
At the Moment I'am trieing to get a log via USB- Monitor. I'm gona post it when I get it...
EDIT2:
OK, cause it's the device of my boss I now gave him mine (after a hard-reset and reinstalltion of the needed application) and reanimated his one by just doing a hard- reset. It came back to live instantly and now I will try to reproduce this hang with his device whilest him using mine. Seems that everybody knows how to reanimate, but nobody knows, why this happens... I'll try to find out and report it back if I can find the reason.
I have the same problem after installing the new HTC Plus plug in.
My ROM is the supa dupa lite one.
Now i need to remember how to do a hard reset!
edit - hard reset go tme back to 'normal'
i tried supa dupa and superstorage dlite, my phone stuck same as you are. .... at last i put any stable .nbh in microsd. then pushed power+ok+soft rest button... reflash back. successful!
Mine with Schaps 4.31 & Radio 1.54 also stucks in Windows Mobile screen after a few day upgrading ROM & radio then installing HTC Plus.
Hard reset does the cure, but I lost all the data.
So what's the culprit ?
i had the same problem, i understood the problem is the calendar.
if you have a schedule in the calendar, with a reminder or with nothing, and you turn off the pda, it will freeze in the windows splash screen when you try to turn it on. Until the schedule is ended.
i had the shap's rom 3.54b, and i resolve installing the 4.30 rom.
bye!
everytime I have had such issues..........was a corrupt installation.
when I am flashing I no touch anything anymore........just gun shy now.
having the same problem, any solutions yet?
Any help would be great....
I have a MDA Compact III issue when trying to upgrade to the ARTEMIS TOUCH 2.1 or 2.0 software
Unfortunatly, my pda was at 49% charge when i first tried, so stage one got to the end, then told me to charge my fone more and ended.
Thus i charge the fone to 75% and re-started. However, upon reconnecting the fone to commence the restart, the USB device was not recognised.
After removing the Active Sync and indeed the USB Driver from the PC and re-installing it, the conenction was re-established, however, it now often drops the connection. Plugging away, i tried the install Step 1 once more, and upon getting to 100% in the cmd part, and then progressing through the wizard, whereby the PDA displayed the progress bar reachinbg 100% (of the unlock stage) the PDA then reboots, and the connection is lost...and doesnt re-establish itself....and then the wizard reports Error [270] : Update Error The image file is corrupted. Please check your update Utility
Now, i have tried various sources for the software, and indeed tried both 2.0 and 2.1.....
Now i have a PDA that intermittantly drops its USB connection (and needs the USB removed and re-added on the PC) and is now slower than it was, plus never got to step 2 to get the software on iot.....
Can anyone help? Else i have a broken phone so to speak.....
Thanks alot in advance
Paul
paulcharles1 said:
Any help would be great....
I have a MDA Compact III issue when trying to upgrade to the ARTEMIS TOUCH 2.1 or 2.0 software
Unfortunatly, my pda was at 49% charge when i first tried, so stage one got to the end, then told me to charge my fone more and ended.
Thus i charge the fone to 75% and re-started. However, upon reconnecting the fone to commence the restart, the USB device was not recognised.
After removing the Active Sync and indeed the USB Driver from the PC and re-installing it, the conenction was re-established, however, it now often drops the connection. Plugging away, i tried the install Step 1 once more, and upon getting to 100% in the cmd part, and then progressing through the wizard, whereby the PDA displayed the progress bar reachinbg 100% (of the unlock stage) the PDA then reboots, and the connection is lost...and doesnt re-establish itself....and then the wizard reports Error [270] : Update Error The image file is corrupted. Please check your update Utility
Now, i have tried various sources for the software, and indeed tried both 2.0 and 2.1.....
Now i have a PDA that intermittantly drops its USB connection (and needs the USB removed and re-added on the PC) and is now slower than it was, plus never got to step 2 to get the software on iot.....
Can anyone help? Else i have a broken phone so to speak.....
Thanks alot in advance
Paul
Click to expand...
Click to collapse
well, I'll just try to give you some suggestions as I don't know much about MDA Compact III ,it does not fall in the category of wizard,it's a Magician device and I'm a wizard k-jam user. anyhow as a general of upgrading is to have your battery fully charged or atleast must have more than 70% charge.cuz during flashing in RUU upgrade mode,it does not charge,so if while during flash something goes wrong or it takes more time to flash,it shud have enough power to go through the whole process.if it does not have enough power to complete the process,it fails to flash properely and thus have a bad flash creating problems.so same has happened with u, you have a bad flash
well in wizards we have certain methods to revive the device or recharge the battery,i have no idea about your device,but can only suggest get the battery charge,secondly your usb connectivity problem is also due to the bad flash,cuz as there is no OS info on the device,it wont be able to establish the connection,which windows are you using,try to upgrade with winxp sp2 and active synchronize ver 4.5
as i have no idea about Magician upgrading method so wont comment further,but advise you to look in the below thread,it might be helpful,cuz its about Magician MDA Compact III
As your posting in the wring forum you might not get much help here,ok
http://forum.xda-developers.com/forumdisplay.php?f=276
good luck
thanks
thanks for the reply. Got it working - used 2.0 to unlock it, and 2.1 for the actual rom upgrade...
I've searched but can't find the answer to this one - sorry if I've missed it somewhere. I have an unmolested T-Mobile UK MDA Vario 2 and I'm trying to install the official TM UK WM6 upgrade ROM.
On my desktop PC (which is properly paired to the phone through ActiveSync to sync with Outlook etc) running the exe results in a grey box with red text saying "Checking files on your PC" forever unless I unplug the phone. Then it will eventually launch the wizard. If I plug the phone in again and wait until it's synced and "Connected", the wizard will go all the way through to checking the existing version and starting the upgrade. However, when the upgrade starts the progress bar stays at 0% and the phone turns off!! Eventually it times out with a 260 error, and no changes have been made to the phone. The PC is running XP, but the only fixes I've seen for the 260 error are if you're running Vista?
I've also tried on my XP laptop - this isn't paired, so the connection through Activesync is just as Guest. The update still does the strange thing with the "Checking files on your PC" box if the phone's plugged in, but unlike the desktop PC the RUU won't talk to the phone at all - connection error before it can even verify the existing ROM version.
Can anyone help? I've been waiting for months to get WM6!
Cheers,
Tim
Phone just turns off?
OK, so now I've done a hard reset on the phone, paired it up to my XP laptop and told it not to sync anything. Now I get to the same stage as I do on the desktop - i.e. the phone switches itself off when the upgrade begins (at 0%), then the RUU times out with an error 260!
One odd thing I noticed is that if I plug the phone in with "Advanced network functionality" enabled (which it is by default) the PC tries to connect it as a new 10mb network card!? However, the RUU does the same thing whether this is enabled or not.
Getting desparate for help now - I've tried 2 different machines and even cleared the phone completely, what more can I do?
Cheers,
Tim
Try flashing from an sdcard. There are quite a post on it here, if you do a quick search you should be able to find the information and hopefully get your device upgraded.
It might be worth installig spl V7 from here before hand just in case anything goes wrong.
http://forum.xda-developers.com/showthread.php?t=296722
Working!
Thanks for the reply. Finally got it flashed using the instructions from here:
http://forums.cingular.com/cng/boar...thread.id=42389&view=by_date_ascending&page=1
Basically, you have to:
- Connect using Activesync and let it finish syncing.
- Start RUU.
- Activesync will close - ignore it and carry on.
- Eventually the phone will go into debug mode.
- Continue through the wizard - it won't be able to identify the existing rom version but this seems to be normal.
- Let it finish!
I was fiddling when Activesync closed - strangely, by disconnecting, restarting AS and reconnecting the wizard carried on and even identified the existing rom properly! It seems that it needs AS to connect to the phone initially, then it closes AS but keeps the USB connection open for the update.
Hope that helps anyone else with the same problem.
Cheers,
Tim
Hey guys,
I have the Bootloader all happy and running but after flashing the Radio (I did this because I thought it would fix random crashes and GPRS crashing) the OS just hangs in boot even after hard resetting.
How do I go about flashing when in Bootloader mode?
Cheers,
Callum
EDIT: I tried with the TTY app (mtty) but it fails to show a USB port. I noticed that Windows XP just sits on acquiring network address.
Hey.
You must deactivate AcitveSync --> "Allow USB Connections" and kill all ActiveSync Processes.
If you have Vista you need other Drivers. Search in google 'VistaRUU'.
You could Flash VIA SD Card from Bootloader, just try to search a little bit in google.
cu
pOpY
If you have installed in the past Hard SPL, you should be able to flash a new ROM from the bootloader screen. Simply choose Hard SPL on the installer.
I have a SIMILAR ISSUE I I have issues with an old Hermes not gonna get into it, but I gotta outta what I thought was my WORST mess ever. Now my 8525 boots (I have the Official AT&T WM6 ROM) see all the opening screens and BOOM it JUST HANGS on the TOUCHSCREEN CALIBRATION screen!!! Touchscreen is completely UNRESPONSIVE so are 90% of the rest of the buttons I can power off and use the side scroll Blackberry dial, and I think the Right SOFT KEY brings UP a USELESS menu, BUT I AM STUCK AT THE CALIBRATION screen no touchscreen I have done A Hard Reset 1000 times, I can connect via ActiveSync with my PC, cant Flash Anything though I get ERROR 260 So I just have a booting 8525 stuck on th4e calibration screen
ANY IDEAS??????????/
nicknowsky said:
I have a SIMILAR ISSUE I I have issues with an old Hermes not gonna get into it, but I gotta outta what I thought was my WORST mess ever. Now my 8525 boots (I have the Official AT&T WM6 ROM) see all the opening screens and BOOM it JUST HANGS on the TOUCHSCREEN CALIBRATION screen!!! Touchscreen is completely UNRESPONSIVE so are 90% of the rest of the buttons I can power off and use the side scroll Blackberry dial, and I think the Right SOFT KEY brings UP a USELESS menu, BUT I AM STUCK AT THE CALIBRATION screen no touchscreen I have done A Hard Reset 1000 times, I can connect via ActiveSync with my PC, cant Flash Anything though I get ERROR 260 So I just have a booting 8525 stuck on th4e calibration screen
ANY IDEAS??????????/
Click to expand...
Click to collapse
check out this link
http://forum.xda-developers.com/showthread.php?t=382578
If you've Hard SPLed your hermes, try the sd card method. 1st, you need to back up your card, format it fat 32 then copy the .nbh file onto from the rom of your choice. rename the nbh file to "Hermimg.nbh" then insert into phone. put hermes into bootloader and follow the prompts. this will reflash another os. Hope this gets you out of your pickle... cheers