HELP!! Im trying to replace my current german language orbit rom with B&B4...activesync was working and my screen went blank like it was supposed to...but I instantly lost activesync when it did...I can not go any farther. What do I do??
I have replied in the other forum, please don't post in more than one forum.
sorry.
I figured it out. Just procede through the USPL setup even though it says make sure activesync is connected. (activesync is dissconnected when screen goes blank but will still update correctly) thanks again guys
of course when your device resets itself activesync connection is lost. even usb connection is lost for a short time (you can hear the ding-dong and dong-ding sound). activesync needs a usb connection and software running both on pc and pocket pc. so when your device starts into bootloader you cant have an activesync connection. but to flash some stuff all you need is a working usb connection.
I can understand that but
I see what your saying...but when your flashing anything be it a PSP, P3300 or anything else where there is a possibility of bricking it, your going to try not to deviate from the instructions...so when the screen goes black and you have to check the box which says you've complied with the above steps and a connected activesync connection is one them...time to hit the forums and get a few things cleared up.
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
Not sure if this was on the fault of my carrier or not, but I actually had this problem before and resolved it once.
I was running 3.60.1 and even tho I had Unchecked "Enable Advanced USB Connection" or whatever under USB to PC in the Connections Tab, My phone would not connect to WMDC (I use Windows Vista). I would just connect to get my contacts via Bluetooth, which worked fine.
I am a heavy user of tethering via USB as I like to charge the phone while I am connected. 3.60 series has been pretty good...I haven't had a complaint really since I upgraded from 3.0 (Which IMO is a bit more stable but I'm not sure why). Every once in awhile, I lose connection. I'm not sure why it does this. I'm using radio 1.48 and I have been using it for both 3.0 and 3.60. I had problems using 1.50 as data connections would drop instantly...so I never caught on to that radio. I am located near the NYC Metro area.
The latest problem I had was...sometimes my data connections would drop and would not reconnect without restarting the phone. I'd SR the phone and all of a sudden during the boot (while still connected to USB), my WMDC picks up the device. Not sure why it chooses to do it after I've had the ROM Flashed for several days now...but I go ahead and set it up only to see my phone assumes a permanent Flight Mode. Under Comm Manager, I am unable to switch back to Phone Mode. I do not have access to Phone settings. I cannot even open my dialer.
I've done it before and I don't save that many new things to my phone...so I went on to HR. After HR...the phone was completely unstable. During the loading of the "customizations" (which correct me if I'm wrong...is the EXTRom), it will install everything and then hang after finishing the last one which I believe was the theme of ATT.tsk.
Frustrated, I decided to flash back to 3.0 I still use 1.40Oli (HardSPL V6) which was always fine and I was never able to update to 2.10Oli for I have weird issues with SSPL and Vista. I do everything normally...I get to the progress screen. It hangs. No problem. Run RUUWrapper again...bootloader screen is accessible and my SPL and HTC_BOOT should be unaffected. Still hangs. I try to flash a radio...hangs. Almost everything I try to flash...hangs.
I've tried multiple USB Cables...thinking that was the problem...same problem though. It gets all the way to the progress and the Bootloader screen recognizes when its plugged to the USB so I don't think that's the problem.
My phone is stuck in bootloader right now and nothing will flash to it. No matter what it will get to progress and load 0% of any NBH I try to flash.
The main point of this post:
1. What caused 3.60.x to not connect to WMDC from the beginning via USB...only to do it randomly later?
2. What caused the corruption to the ROM leading me "GSM-less" stuck in Flight Mode and no access to anything to turn it back on to Phone Mode?
3. What is the cause of my phone not updating any NBHs I try to flash (OS Only/Radio Only/Original Shipped) ROMs?
I'm not sure if I was the only one receiving these errors. I have not updated my signature in awhile but I was running:
HARD-SPL V6: 1.40.Oli
Radio: 1.48.00
ROM: VP3G 3.60.1
Thanks for your help in advance.
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...
Just got my rhodium today (t-mobile branded unfortunately), it's a great device. Just one weird problem i am having with activesync, maybe someone knows what the problem is.
After installing activesync it works fine, untill I turn off (restart) my computer, then as soon as a connect my rhodium it tries to intialize the connection but gets an error. On the device it says, error with rapiclnt and asks me to send the error log to Microsoft. When i run the active sync troubleshooter it says that connection with the device cannot be established and over some suggestions (stop firewall,enable usb connection).
So far the only thing that fixes it, is uninstalling and reinstalling activesync. It then works fine untill i restart.
Things i have tried that have not worked are:
1. Hard reset the device
2. Soft reset the device
3. Deleted partnerships on both computer and device
4. Removed firewall
5. Unchecked advanced network functionality
The only other thing I can think of is to formate my pc and do a complete fresh install of windows xp. If nothing else this should rule out the problem is on the pc end I think.
Any suggestions are appreciated, thnx in advance.