View Full Version : error [260] message every time
deejacker
27th August 2007, 07:49 PM
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)
T-Rob
27th August 2007, 07:54 PM
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
deejacker
27th August 2007, 07:59 PM
I am assuming you mean flash with the new ROM, sammy's in my case?
T-Rob
27th August 2007, 08:01 PM
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)
deejacker
27th August 2007, 08:04 PM
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.
deejacker
27th August 2007, 08:08 PM
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.
T-Rob
27th August 2007, 08:36 PM
What operating system en activesync are you using?
deejacker
27th August 2007, 08:46 PM
On the PC I am using XP and Activesync 4.5
T-Rob
27th August 2007, 08:52 PM
Check your connection settings to accept USB connections. Also, try using Hard-SPL 1.30 before flashing the ROM again.
jotam
27th August 2007, 08:59 PM
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.
In your PC, try another USB connection.
deejacker
27th August 2007, 09:07 PM
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.
nealed
27th August 2007, 09:08 PM
Using Vista? if so which version?
rparslow
28th August 2007, 12:14 AM
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
rparslow
28th August 2007, 01:02 AM
It works :D
Now to discover the joys of WM6 after only having WM5 for two weeks....
steveecourt
29th August 2007, 12:35 AM
/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
racerx_
29th August 2007, 01:56 AM
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?
steveecourt
29th August 2007, 08:51 PM
This seems to be on any rom bar the Dopod roms
and it says 260 connection error
nealed
29th August 2007, 09:50 PM
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.
Almulatham
30th August 2007, 07:49 AM
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
borislavvs
26th September 2008, 04:55 PM
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)
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
stormyb
26th September 2008, 05:58 PM
htc diamond?
you're in the wrong forum...
enadiz
20th April 2010, 05:20 PM
the replug thing worked like a charm on my hd2! THANKS
SuperSport
21st April 2010, 06:58 PM
If all else fails, and sometimes it does... ...Enter TriColorScreen mode and flash the OEM ROM back on. Then re-Flash the Hard SPL, and then your desired ROM & Radio. This should work most of the time.
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.